-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CORS Error for (some) Firefox Users #429
Comments
Thank you for reaching out to us. I've checked the thread, and it is not issue with PubNub service certificate, which you can check through the request to the mentioned subscribe call (issued for Also double-checked that the service doesn't have any issues with preflight ( If a browser reports CORS issues, it means that the server didn't return
|
OK, thanks for checking that it is really most likely on the Clientside. |
We are Logging Frontend Errors in the Browser an we always have these PNBadRequestCategory in our logs. Several thousand Times a Day. All from Firefox Users.
Object { error: true, category: "PNBadRequestCategory", operation: "PNSubscribeOperation", statusCode: 0, errorData: TypeError } category: "PNBadRequestCategory" error: true errorData: TypeError: NetworkError when attempting to fetch resource. columnNumber: 1 fileName: "" lineNumber: 0 message: "NetworkError when attempting to fetch resource." stack: "" <prototype>: TypeError.prototype { stack: "", … } operation: "PNSubscribeOperation" statusCode: 0
We also get this Error in the DevConsole
CORS Error (Cross-Origin): https://ps20.pndsn.com/v2/subscribe/sub-c-c356f98c-4451-xxx/0?heartbeat=300&tt=17368668493230380&tr=41&uuid=xxx&requestid=bc93eed9-bac6-49ce-a60b-d8972518cee6&pnsdk=PubNub-JS-Web%2F8.3.2.
It is not a general Problem for all Firefox Users. All other Browsers are also fine.
We can reproduce the Error when we are in our VPN behind the Firewall. After one Minute or so this Error pops up in the DevConsole.
This MIGHT be something with our Firewall unpackaging the HTTPS Request to do some DPI. It will repackage the Request with a self signed Certificate. This seems to cause trouble in Firefox according to this Stackoverflow: https://stackoverflow.com/questions/24371734/firefox-cross-origin-request-blocked-despite-headers
The Request Header look fine. Its the same Header as for the successfull Responses (without the Firewall).
(I shortend some entries with xxx for this Issue)
Is there anything that we can do to help our Firefox Customers that are apperently also behind a Firewall, or somehow get this CORS Error?
The text was updated successfully, but these errors were encountered: