EAP7 - Internal Web Server and CSS

I am not sure if this is a bug or I am doing something wrong, but..

I right click on my index.html and Open in Browser.. starts up the internal webserver
http://localhost:63342/projectname/index.html and none of the relative css files styles apply (css/stylesheet.css)
i see them in the web inspector loaded fine, but none applied to the DOM objects. (chrome or firefox same behavior)

i open the file directly in browser (eg file:// ) they are all fine and i make them absolute to a remote webserver and they load fine, so that makes me think it is a bug somehow with the local webserver.


Comment actions Permalink

i'm guessing it is the mimetypes on the built in server?
because the js quite often gives me warnings like "Resource interpreted as Script but transferred with MIME type application/octet-stream" as well

Comment actions Permalink


can you provide the sample project that shows up the problem? Relative urls works fine for me when html is being served on built-in server

Best regards,

Comment actions Permalink

newest firefox says:

[16:28:22.913] The stylesheet http://localhost:63342/projectname/css/stylesheet.css was not loaded because its MIME type, "application/octet-stream", is not "text/css". @ http://localhost:63342/projectname/#/login

is it maybe because this was an upgraded project from a previous version?
or does internal webserver not respect MIME types?

i am using webstorm on OSX 10.8.4

Comment actions Permalink

must be something about it being an upgraded project

when i make a new project from scratch it sends CSS file as MIME type "text/plain"
when i add to existing it sends it with a MIME type "application/octet-stream"

not sure how to fix this

Comment actions Permalink

Well ... delete .idea subfolder in that problematic project (while project is closed in IDE; make backup first if desired), then use "Open Directory" from Welcome screen and point to your project folder. Now you need to re-configure it from scratch (which should not take long at all).


Please sign in to leave a comment.