-
Notifications
You must be signed in to change notification settings - Fork 175
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
now.js transferred as 'text/plain'? #18
Comments
sorry, it's chrome 10, not firefox |
Thanks for letting us know. It's added to the list of bugs to fix. |
Frankly, there should be an option to relay serving static files to an external app (nginx?) or a middleware layer -- to say, to the code which is capable of setting etags,cache-control and so on. For setting SERVER and PORT is in essense the same as the rendering a template, right? |
now.js content-type 'text/plain' has been changed to 'text/javascript' This issue is now fixed. @dvv, we set SERVER and PORT on first request of now.js, then we cache it since it will never change in the lifetime of the service instance. |
This still leaves unnecessary checks for certain URLs ('/nowjs/now.js') in request handlers in setups like mine where dynamic handlers stand before static ones. I mostly meant elimination of these checks. The same in socket-io itself about checking whether url is /socket.io/socket.io.js which is not switchable out and just eats ticks... |
I'm using firefox 4.0rc2. A warning "Resource interpreted as Script but transferred with MIME type text/plain." triggered when loading now.js.
The text was updated successfully, but these errors were encountered: