Skip to content
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 headers missing for 404'd routes #167

Open
robbiemu opened this issue Apr 27, 2017 · 3 comments
Open

CORS headers missing for 404'd routes #167

robbiemu opened this issue Apr 27, 2017 · 3 comments

Comments

@robbiemu
Copy link

robbiemu commented Apr 27, 2017

editor's note: CORS headers should still happen on 404'd resources...

edit: please close this issue. I was calling https://wzrd.in/standalone/[email protected] instead of https://wzrd.in/standalone/react-redux@latest. My apologies.

I'm getting:

(index):1 XMLHttpRequest cannot load https://wzrd.in/standalone/[email protected]. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://robbiemu.github.io' is therefore not allowed access. The response had HTTP status code 502.

which is weird because when I load the url directly I see a cors response header in the network tab:

Access-Control-Allow-Origin:*
Connection:keep-alive
Content-Length:77297
Content-Type:text/javascript
Date:Thu, 27 Apr 2017 18:39:38 GMT
Server:nginx/1.11.3
Strict-Transport-Security:max-age=31536000; includeSubDomains; preload
X-Powered-By:Express
@jfhbrook
Copy link
Collaborator

Try removing the .js

@jfhbrook
Copy link
Collaborator

all good!

@jfhbrook jfhbrook changed the title CORS with github.io? CORS headers missing for 404'd routes Apr 27, 2017
@jfhbrook
Copy link
Collaborator

Reopening because I think that 404s should also have proper CORS headers.

@jfhbrook jfhbrook reopened this Apr 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants