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 interacting with an iframe embedded on a page, and clicking a button inside the iframe, an AJAX request is made with a different origin. However, the cookie header is not included in the request when it should be, leading to incomplete functionality.
Interact with the iframe (click a button inside it) that triggers an AJAX request.
Observe the request headers in the browser's developer tools.
What did you expect to happen?
I expected the Cookie header to be present in the AJAX request header when the request is sent from the iframe, especially when it is a different domain.
Version
3.x
What browser are you seeing the problem on?
Chrome
Relevant log output
When the iframe and its content originate from different domains (using ngrok), the request header looks like this:
What happened?
When interacting with an iframe embedded on a page, and clicking a button inside the iframe, an AJAX request is made with a different origin. However, the cookie header is not included in the request when it should be, leading to incomplete functionality.
Steps to reproduce the issue:
Expose local development server (running on http://localhost:80) to the internet using ngrok.
Run the following command: ngrok http 80. This will forward traffic from a public URL (e.g., https://4c37-2404-c0-2a10-00-1c16-c496.ngrok-free.app) to local server (http://localhost:80).
Embed the iframe with the following code in https://4c37-2404-c0-2a10-00-1c16-c496.ngrok-free.app page:
Interact with the iframe (click a button inside it) that triggers an AJAX request.
Observe the request headers in the browser's developer tools.
What did you expect to happen?
I expected the Cookie header to be present in the AJAX request header when the request is sent from the iframe, especially when it is a different domain.
Version
3.x
What browser are you seeing the problem on?
Chrome
Relevant log output
When the iframe and its content originate from different domains (using ngrok), the request header looks like this:
When the iframe and its content originate from different domains (without using ngrok), the Cookie header is properly set in the request:
The text was updated successfully, but these errors were encountered: