Reaching the end of my rope, so I thought I'd check here to see if anyone
has experienced anything similar.
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',
'
I would expect NGINX to be doing some level of caching based on the ETag,
but I would also expect it to be using the Content-Type as part of the
cache validation, which is controlled by the Vary header.
Here's a reasonable looking article (I only skimmed) on it that might give
you enough backgroun
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':
I just disabled nginx, added 'Content-Type' back into my node app, cleared
my browser cache and fired up node without nginx. All headers now appear.
Funny thing, I went to the Nginx IRC channel looking for ideas, and they
immediately talked me back into my node app being the problem.
Now I need
Thank you for the responses. I did not read the article posted, but I did
run the node app without nginx just now, and I think all header entries now
appear as they should. I'm rushing through this while at work with limited
tools, therefor the "I think" part. But it does seem to now point to ng
