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

JS and CSS pages return 404 error #132

Closed
neoncitylights opened this issue Dec 14, 2013 · 7 comments
Closed

JS and CSS pages return 404 error #132

neoncitylights opened this issue Dec 14, 2013 · 7 comments

Comments

@neoncitylights
Copy link
Contributor

neoncitylights commented Dec 14, 2013

Whenever I try to review CSS or JS pages, it returns a 404 error and says "404 Not Found".

@georgebarnick
Copy link
Member

georgebarnick commented Dec 15, 2013

This is an issue with all JS and CSS pages, not just those in the interface namespace.

@neoncitylights
Copy link
Contributor Author

neoncitylights commented Dec 15, 2013

Oh, okay, I changed it.

@georgebarnick
Copy link
Member

georgebarnick commented Dec 15, 2013

@neoncitylights
Copy link
Contributor Author

neoncitylights commented Dec 15, 2013

Odd, looking at http://cuusoo.brickimedia.org/wiki/Special:Log/move I don't see log actions that are moving pages like these with a redirect.

@georgebarnick
Copy link
Member

georgebarnick commented Dec 15, 2013

@codyn329: Special:NewPages appends that parameter in every link in the event one has been moved so that it can still be patrolled. That's not the issue.

In any event, it's not actually redirect=no that's letting it load, it's using the real URL, such as http://meta.brickimedia.org/index.php?title=MediaWiki:Refreshed.css. The short URL is what prevents it from loading it seems, so the issue is most-likely in an nginx configuration.

@SirComputer1
Copy link
Contributor

SirComputer1 commented Dec 15, 2013

@lewiscawte knows most about Nginx config, and stated on Skype he is looking into it.

@ghost ghost assigned lewiscawte Dec 15, 2013
@lewiscawte
Copy link
Member

lewiscawte commented Dec 20, 2013

Fixed it, I generated a new Nginx short URL config which is now in place. It needs a bit of cleaning up but this can be closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants