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

CSS files returned with corrupted headers #48

Closed
jlap opened this issue Nov 14, 2013 · 2 comments
Closed

CSS files returned with corrupted headers #48

jlap opened this issue Nov 14, 2013 · 2 comments
Labels
bug

Comments

@jlap
Copy link
Contributor

@jlap jlap commented Nov 14, 2013

Sometimes, a css file is returned and the Content-Type in the response Headers is wrong.

Examples:
Content-Type http://127.0.0.1/ScribeUI
Content-Type Apache/2.2.22
Content-Type /usr/local/etc/mime.types
Content-Type application/x-go-sgf

This problem happens very intermittently and pretty randomly.

In flask's helpers.py, in the send_file function, I tried adding this as a debug message:

pprint.pprint(filename_or_fp+' '+mimetype)

But at this point, the file's mimetype is all good.

I was able to find someone with a similar problem: https://groups.google.com/forum/#!topic/web2py/5F3UUMkDPRI

We both use Flask and mod_wsgi, that's pretty much all we have in common. But otherwise, it's exactly the same issue.

A CSS file having this issue won't be rendered by firefox. But if you open it, the content is there. The only problem is the corrupted content-type.

@jlap
Copy link
Contributor Author

@jlap jlap commented Nov 15, 2013

Issue is solved by using mod_wsgi 3.4 ( see https://code.google.com/p/modwsgi/issues/detail?id=255 )

I will updated the readme and the website to reflect this new requirement.

@jlap
Copy link
Contributor Author

@jlap jlap commented Nov 22, 2013

Closed with warnings in fd36860

@jlap jlap closed this Nov 22, 2013
@jlap jlap mentioned this issue Mar 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.