14 messages in ru.sysoev.nginxRewrite Response Headers
FromSent OnAttachments
"Kyrre Nygård"Dec 10, 2008 9:16 am 
Redd VinyleneDec 10, 2008 10:13 am 
Igor SysoevDec 10, 2008 10:55 am 
Redd VinyleneDec 10, 2008 11:12 am 
Igor SysoevDec 10, 2008 11:19 am 
Redd VinyleneDec 10, 2008 12:08 pm 
Igor SysoevDec 10, 2008 12:24 pm 
Redd VinyleneDec 10, 2008 1:06 pm 
Igor SysoevDec 11, 2008 12:12 am 
Redd VinyleneDec 11, 2008 1:07 am 
Igor SysoevDec 11, 2008 1:19 am 
Redd VinyleneDec 11, 2008 1:42 am 
Redd VinyleneDec 11, 2008 4:30 am 
Timothy A. NapthaliDec 12, 2008 3:40 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Rewrite Response HeadersActions...
From:Timothy A. Napthali (timo@napthali.com)
Date:Dec 12, 2008 3:40:23 pm
List:ru.sysoev.nginx

I'm wondering if Nginx is going to get the ability to add, remove and rewrite
generic response headers?

At the moment you seem to be able to use "add_header" when the response code is
200, 204, 301, 302 or 304 or modify the "expires" header but what I would like
to be able to do is muck about with authentication headers. I'm trying to get
Microsoft "Outlook Anywhere" (aka RPC over HTTP) to work but one of the issues
I'm having is negotiating authentication away from NTLM (which wont work) to
basic. I've seen this done with Apache by doing response header rewrites to
strip out the NTLM stuff in a few examples.