Axios not sending proper request type

I'm working on a project where I send an AJAX request using Axios to an external endpoint that also requires an authorization header.

const axios = require('axios');

axios.interceptors.request.use(request => {
    console.log(request);
    return request;
});

function printResponse(response){
    console.log("\nResponse-Body\n---\n\n" + JSON.stringify(response.data) + "\n");
};

function printSection(name,data){
    console.log("<" + name + ">\n---\n");
    console.log(data);
    console.log("\n===\n");
};

const id = 131;

const request = {
    url: `https://website.com/api/endpoint/${id}`, //Changed URL for this example.
    method: "delete",
    headers: {
        Authorization: "Authorization-Information" //Changed real value for this example.
    }
};

// GET request works.
// POST request works.
// DELETE request does not work.
// PATCH request does not work.

const query = axios(request).then((response)=>{

    printSection('response.request',response.request);

    /*
    console.log("===<REQUEST>===\n");
    printSection('method',request.method);
    printSection('headers',request.headers);
    console.log("===</REQUEST>===\n");

    console.log("===<RESPONSE>===\n");
    printSection('request.method',response.request.method);
    printSection('request._headers',response.request._headers);
    console.log("===</RESPONSE>===\n");
    */

},(error)=>{
    console.log("Error");
    console.log(Object.getOwnPropertyNames(error));
    printSection('response',error.response);
    printSection('request',error.request);
});

When I use this to do a request to the endpoint, I am seeing that the response.request.method shows this was a GET request rather than a DELETE request, and the same happens when I try to use a PATCH request. Using a GET and POST request works perfectly fine though.

So, I then setup an Express.js server with some very simple code

const express = require('express');
const server = express();
const PORT_NUMBER = 3000;

server.all('/',(request,response)=>{
    response.send("Hello World");
    console.log(request.headers);
    console.log('\nMethod: ' + request.method + "\n");
    console.log(request);
    console.log("\n---\n");
});

server.listen(PORT_NUMBER,function(){
    console.log("The server is listening at 127.0.0.1:" + PORT_NUMBER + "\n");
});

To see if it may be the endpoint server's fault. It appeared that the request types were correct when they were being made towards this express server, and nothing funny was showing up. So then I attempted to do an AJAX request from within a chrome browser window using the following code

<html>
<body>
    <head>
        <script src="https://code.jquery.com/jquery-3.2.1.min.js" integrity="sha256-hwg4gsxgFZhOsEEamdOYGBf13FyQuiTwlAQgxVSNgt4=" crossorigin="anonymous"></script>
    </head>
    <script>
        function report(data,status){
            console.log('status: ',status);
            console.log(data);
        };

        var getTaskList = {
            url: 'https://website.com/api/endpoint/',
            method: 'GET',
            headers: {
                Authorization: "Authorization-Information"
            } 
        };

        var patchTask = {
            url: 'https://website.com/api/endpoint/id',
            method: 'PATCH',
            headers: {
                Authorization: "Authorization-Information"
            },
            data: {
                "prop_1": true,
                "prop_2": "3",
                "prop_3": "Edited.",
                "prop_4":10
            }
        };

        $(document).ready(function(){
            $.ajax(patchTask).then(function(data,status){
                report(data,status);
            });

        });
    </script>
</body>
</html>

After which I then change the AJAX request to the 'getTaskList' JSON object and use that to see if my PATCH request has updated the object. When calling this from within the browser, the PATCH call was successfully processed and even a DELETE call worked.

So what could be going wrong here that's making the endpoint server believe it is receiving a GET request with this code?