NameTrans fn="redirect" a Connection: close header

When you use NameTrans fn="redirect" a Connection: close header is always added to the redirect.Is there some way to avoid this?

If you know that you are redirecting to the same server you do not need to close the connection.

We have seen that from some parts of the world it adds an additional second to the transaction.

[341 byte] By [mshamber001a] at [2007-11-27 4:13:26]
# 1

I'm not aware of any way that NameTrans fn="redirect" could interfere with keep-alive. I used the following NameTrans directive with 7.0:NameTrans fn="redirect" from="/foo" url="http://www.example.com/bar"With the above NameTrans directive, I tried the following request:GET /foo HTTP/1.1

Host: www.example.comI got a response that indicated the connection could be kept open:HTTP/1.1 302 Moved Temporarily

Server: Sun-Java-System-Web-Server/7.0

Date: Sun, 13 May 2007 21:52:04 GMT

Location: http://www.example.com/bar

Content-length: 0

Content-type: text/htmlNote that there's no Connection: close header.

Can you give an example where NameTrans fn="redirect" causes the server to send a Connection: close header?

elvinga at 2007-7-12 9:19:40 > top of Java-index,Web & Directory Servers,Web Servers...
# 2

Hi,

Here is example.Happens with both our 301 and 302 redirects.

www.nokia.com/softwareupdate

<Client uri="/softwareupdate" urlhost="www.nokia.com">

Output fn="set-variable" error="301" noaction="true"

NameTrans fn="redirect" from="/softwareupdate" url-prefix="http://europe.nokia.com/softwareupdate"

</Client>

GET /softwareupdate HTTP/1.1

Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */*

Accept-Language: en-us

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1)

Host: www.nokia.com

Connection: Keep-Alive

Cookie: CP=null*; SMSESSION=aohSPbGAGMtSC1Chl/xE9bFJP9zXNfh9Ay+NemUydfGAgK9zKqZykOYndgsh

HTTP/1.1 301 Moved Permanently

Date: Mon, 21 May 2007 19:22:34 GMT

Content-Type: text/html

Connection: close

Server: "Nokia"

Location: http://europe.nokia.com/softwareupdate

Via: 1.1 saec-nokiap11ca (NetCache NetApp/6.0.5)

mshamber001a at 2007-7-12 9:19:40 > top of Java-index,Web & Directory Servers,Web Servers...
# 3
Uhm, that Connection: close header appears to have been added by a NetApp NetCache appliance. There's nothing Web Server can do to prevent downstream devices from modifying its response.
elvinga at 2007-7-12 9:19:40 > top of Java-index,Web & Directory Servers,Web Servers...