Re: Send Strict-Transport-Security header in 401 response

2016-06-22 Thread Thomas Glanzmann
Hello Francis, * Francis Daly [2016-06-19 11:57]: > http://nginx.org/r/add_header > That suggests that you can use an "always" parameter. > Is that appropriate in this case? yes, thank you a lot. That solved my problem. Cheers, Thomas ___ n

Re: Send Strict-Transport-Security header in 401 response

2016-06-19 Thread Francis Daly
On Sun, Jun 19, 2016 at 11:51:28AM +0200, Thomas Glanzmann wrote: Hi there, > I would like to send the header: > > add_header Strict-Transport-Security "max-age=31536000; includeSubDomains"; > > Despite the 401 Unauthorized request. Is that possible? http://nginx.org/r/add_header That suggest

Send Strict-Transport-Security header in 401 response

2016-06-19 Thread Thomas Glanzmann
Hello, I would like to send the header: add_header Strict-Transport-Security "max-age=31536000; includeSubDomains"; Despite the 401 Unauthorized request. Is that possible? Currently the header is only added after a successful authorization: (x1) [~] curl -v https://tuvl.de * Rebuilt URL to: htt