I downloaded another file and the Content-Disposition header lists the filename with space under quotes correctly "zcs error.docx" thereby proving that its nginx which is not parsing it correctly. Correct me if i am wrong.
1. Cache-Control: no-store, no-cache 2. Connection: keep-alive 3. *Content-Disposition: attachment; filename="zcs error.docx"* 4. Content-Encoding: gzip 5. Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name="zcs error.docx" Thanks -Kunal On Mon, Mar 24, 2014 at 11:16 AM, Lukas Tribus <luky...@hotmail.com> wrote: > Hi Kunal, > > > > I used the web browser but didn't see this Content-disposition header > > in the response. Only saw these response headers. > > We need to see the Content-disposition, everything else makes no sense. > > Are you trying against the nginx frontend or your backend? If it is nginx > you're connecting to, you abviously need a filename without spaces > otherwise > the response will not show up on your browser. > > > > > Using the curl to get the file directly from the backend server keeps > > throwing the http 404 must authenticate error don't know why as i am > > supplying the -u username:password as well > > Fix your authentication problem. Only you know how your backend > authenticates users, we can't tell you that (perhaps you need cookies). > > > > Regards, > > Lukas > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
