You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When gatling does a preflight request, so using the method OPTIONS, it also sends the cookie. By standards, cookies shouldn't be sent for preflight requests. So Gatling should avoid sending the cookies.
I have a case that cookies are handled in the backend, but they shouldn't as in reality cookies are never added to those requests.
The text was updated successfully, but these errors were encountered:
The thing here is that Gatling does't have built-in support for CORS and preflight requests.
You're using a generic OPTIONS request that only abides to the HTTP specification, not the CORS or Fetch ones.
I'm not found of adding something like isPreflight method on generic HTTP requests. What would be great would be to add a withPreflight method that would take care of automatically generating the preflight request.
Is this something you would be interested in contributing or sponsoring?
slandelle
changed the title
Cookie sent with preflight / options request
HTTP: Built-in support for CORS preflight requests
Sep 22, 2023
When gatling does a preflight request, so using the method OPTIONS, it also sends the cookie. By standards, cookies shouldn't be sent for preflight requests. So Gatling should avoid sending the cookies.
I have a case that cookies are handled in the backend, but they shouldn't as in reality cookies are never added to those requests.
The text was updated successfully, but these errors were encountered: