I used the web browser but didn't see this Content-disposition header in
the response. Only saw these response headers.


1. Response Headersview source
1. Connection:
keep-alive
2. Content-Length:
1159
3. Content-Type:
text/html
4. Date:
Mon, 24 Mar 2014 17:15:00 GMT
5. Server:
nginx


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

kunal@zdev-vm048:~$ curl -u testuser1:testpass -k -I "
https://127.0.1.1:8443/service/home/~/?auth=co&loc=en_GB&id=259&part=3"

*HTTP/1.1 404 must authenticate*

Date: Mon, 24 Mar 2014 17:38:56 GMT

Content-Type: text/html; charset=ISO-8859-1

Cache-Control: must-revalidate,no-cache,no-store

Content-Length: 320


Thanks

-Kunal


On Mon, Mar 24, 2014 at 3:56 AM, Lukas Tribus <luky-37@hotmail.com> wrote:

> Hi,
>
>
> > What debugs should i enable & how to see these response headers ? I do
> > see this error though.
>
> Just use curl for example and request it directly from your backend:
> curl -k -I "
> https://127.0.1.1:8443/service/home/~/?auth=co&loc=en_GB&id=259&part=3"
>
>
> So you can check the actual response header.
>
>
>
>
> 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