-
Bug
-
Resolution: Not a Bug
-
Major
-
fuse-7.7-GA
-
None
-
False
-
False
-
-
Undefined
-
Fuse Standalone
-
-
This is an issue related with the "enableCORS" option comes with the "restCofiguration".
Let's say user send an "OPTIONS" request(preflight request) with a request parameter, "id":
curl -v --location --request OPTIONS 'http://localhost:8080/reproducer/example?id=bob'
Camel will store this request parameter in Exchange.header.
The problem is a response for this OPTIONS request. It contains the request option, "id", as a response header.
This behavior will bring ERR_INVALID_HTTP_RESPONSE error on some browser.
For example, if Japanese character(whitespace) is passed on chrome browser, the ERROR occurs on the browser.
In an OPTION request reply, please do not contain request parameter as a response header.