Context Broker Preflight OPTIONS request

问题

I'm trying to make a GET request to a Context Broker instance from a browser.

I've enabled CORS on the CB using the -corsOrigin __ALL flag when starting the app, and I can see that this has worked by making a request in POSTMAN and seeing this header in the response: access-control-allow-origin →*.

I need to specify the Fiware-Service header in my GET request in order to get the correct entities, which I believe is making the request not simple, triggering an OPTIONS HTTP request.

Inspecting the outgoing request, Chrome reports that these headers are sent:

Access-Control-Request-Headers: fiware-service
Access-Control-Request-Method: GET

The response I get from the Context Broker is:

Request URL: http://xxx.xxx.xxx.xxx:1026/v2/entities/
Request Method: OPTIONS
Status Code: 405 Method Not Allowed

A previous answer by McMutton, to a similar question stated:

"do the necessary changes on your js code to make sure your request falls within the scope of simple requests."

Which was directed at removing non-standard headers from the request. However, for me I cannot see any non-standard headers being sent.

Reading the Fiware documentation on Access-Control-Allow-Headers, there is a link to the source code where the allowed headers are specified. There, I can see the Fiware-Service header defined, but it does not case-match the headers being sent from the browser (the browser has converted my headers to all lower case).

Does anyone know if "the headers check" in the Context Broker is case-sensitive?

If not, what else could be the issue?

Edit: this issue seems to have been reported here: https://github.com/telefonicaid/fiware-orion/issues/3453

回答1:

Based in the discussion on the associated github issue it seems the problem is due to Context Broker is pretty old (version 1.7.0) and that feature wasn't developed yet in that version.

The solution is to update Context Broker to the most recent version (2.2.0 at this moment).

回答2:

Thanks @fgalan, yes the feature is included in the latest Context Broker version. However, our system is currently quite fragile, so until we can confidently re-build and migrate to the newer version I'm going to mock the HTTP response for the options request using NGINX.

This configuration listens for requests on a different port to the Context Broker, and sends a success response when OPTIONS HTTP requests arrive.

If it's not an OPTIONS HTTP request, NGINX forwards the request to the Context Broker instance.

server {
    listen 1885;
    listen [::]:1885;

    location / {
        if ($request_method = OPTIONS ) {
            add_header Content-Length 0;
            add_header Content-Type text/plain;
            add_header 'Access-Control-Allow-Origin' '*';
            add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS';
            add_header 'Access-Control-Allow-Headers' 'Fiware-Service';
            return 204;
        }
        proxy_pass http://xxx.xxx.xxx.xxx:1026;
        proxy_set_header Host      $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

来源：https://stackoverflow.com/questions/57491353/context-broker-preflight-options-request

标签

fetch

fiware

fiware-orion

preflight

context-broker