Hi Brian, It looks like you corrected the Content-Type... this is what I'm seeing: ~ » curl -I http://webebenezer.net/build_integration.html HTTP/1.1 200 OK Server: nginx/1.2.7 Content-Type: text/html Accept-Ranges: bytes Content-Length: 3479 Last-Modified: Fri, 15 Mar 2013 21:34:36 UTC Connection: keep-alive (the -I switch shows the http headers, which is what your browsers uses to determine how to handle the content). On my nginx server, which is from the Ubuntu repository, I have a file called /etc/nginx/mime.types, which contains a map of file extensions and their corresponding mime types: erikm at linode:/etc/nginx$ cat mime.types types { text/html html htm shtml; text/css css; text/xml xml rss; image/gif gif; image/jpeg jpeg jpg; [...] video/x-ms-wmv wmv; video/x-msvideo avi; } This file is included in nginx.conf: erikm at linode:/etc/nginx$ grep -R mime.types * nginx.conf: include /etc/nginx/mime.types; Hope that helps! -Erik On Wed, Mar 20, 2013 at 11:11 AM, Michael Moore <stuporglue at gmail.com> wrote: > On Wed, Mar 20, 2013 at 10:59 AM, Brian Wood <woodbrian77 at gmail.com> wrote: >> When I click on the links to source code here -- >> http://webEbenezer.net/build_integration.html >> , Chrome downloads the file contents. >> I'm not sure, but may have seen that with >> another browser also. Is that something that's >> changed? I have a link to an archive on that >> page that can be downloaded which has all of >> the files linked to on that page. So I don't want >> a browser to download individual files,but to >> display the contents of the file on the screen. >> Tia. > > That page is telling the browser that the content is of type > "application/octet-stream". Since Chrome doesn't know how to display > application/octet-stream, it prompts you to download it. > > What changed could be the browser, the server, or your memory :-) > > It could be that the browser's default behavior changed from showing > application/octet-stream as plain-text to downloading. > It could be that the server changed from sending the files as > text/plain to application/octet-stream. > It could be that you only thought you remembered it working that way. > > -- > Michael > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list -- Erik K. Mitchell erik.mitchell at gmail.com