, 8 March 2016, Krishna Kumar K K
mailto:kris...@brocade.com>> wrote:
I am able to modify the set-cookie header from the server to flag it secure. I
am trying to do the same in the request header as well.
Those flags are instructions to client. They don't have meaning on request
heade
Subject: Re: secure and httponly cookies
On Mon, Mar 07, 2016 at 09:50:00PM +, Krishna Kumar K K wrote:
Hi there,
> I have tried exactly the same as in this page:-
>
> proxy_cookie_path / "/; secure; HttpOnly";
>
> it sets the flags on the cookie in the response header,
-IP $remote_addr;
proxy_set_headerX-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_headerX-Forwarded-Proto $scheme;
proxy_pass http:///;
proxy_read_timeout 90;
}
}
-Original Message-
From: Krishna Kumar K K
Sent: Monday, March 07, 2016 1:50 PM
To: nginx@ngin
I have tried exactly the same as in this page:-
proxy_cookie_path / "/; secure; HttpOnly";
it sets the flags on the cookie in the response header, but when I refresh the
page, it is sending the cookies in the requests header without these flags, it
just resets it.
Thanks,
Krishna
-Origina
Hi,
My set up is as below:
NGINX (reverse proxy) -->IBM WebSeal (redirects to a common login page, after
authentication forwards to internal proxy along with the redirected url) -->
Internal Proxy (IBM http Server) --> WebSphere Portal.
I am trying to access
https:///wps/seedlist/myserver?Sou
