On Jun 22, 2015, at 9:14 AM, Ecas Saeculum wrote:
> Simple HTTP Server, that responds on connection with a write head and
> response.end('hello'); Simple, simple.
>
> When I do this:
>
> response.writeHead(200, {
> 'Content-Type': 'text/plain',
> 'ETag': 'someETagHash',
> 'Content-Size': '10'
> });
>
>
> web page header has Content-Type and Content-Size.
>
> When I remove Content-Type:
>
> response.writeHead(200, {
> 'ETag': 'someETagHash',
> 'Content-Size': '10'
> });
>
> Web page receives the ETag.
>
> I'm using nginx as reverse proxy, and nginx is sending no headers to the
> client. Node.js 0.10, no other packages.
>
> Just checking to see if anyone else has seen something similar. I have almost
> 20 hours into troubleshooting this and I'm probably just going to run without
> a Content-Type, if no one has seen something like this. I've tried escaping
> and quoting each/all entries every way I can think of. I've cleared out my
> nginx config to bare bones. I'm not seeing any ill effects without a
> Content-Type, but it is kind of an annoying issue.
Content-Type seems like a pretty important header to send, no?
Does this problem occur if you access your node app directly, and do not
reverse proxy through nginx?
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/4F03A18E-F62C-46DF-B7A8-CA7D9393023D%40ryandesign.com.
For more options, visit https://groups.google.com/d/optout.
