Received: (qmail 31022 invoked by uid 501); 21 Dec 2001 17:49:35 -0000
Message-Id: <20011221174935.31021.qmail@apache.org>
Date: 21 Dec 2001 17:49:35 -0000
From: Jason Terry <jter@cartmanager.net>
Reply-To: jter@cartmanager.net
To: submit@bugz.apache.org
Subject: nokeepalive doesn't properly change the HTTP_CONNECTION env variable
X-Send-Pr-Version: 3.110

>Number:         9224
>Category:       mod_setenvif
>Synopsis:       nokeepalive doesn't properly change the HTTP_CONNECTION env variable
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Dec 21 09:50:00 PST 2001
>Closed-Date:    Fri Dec 21 10:32:43 PST 2001
>Last-Modified:  Fri Dec 21 10:32:43 PST 2001
>Originator:     jter@cartmanager.net
>Release:        1.3.22
>Organization:
>Environment:
RedHat 7.2 (uname below)
Linux server.cartmanager.net 2.4.9-13smp #1 SMP Tue Oct 30 19:57:16 EST 2001 i686 unknown
>Description:
When using the below line in my httpd.conf
BrowserMatchNoCase ".*MSIE.*"   nokeepalive

I see that the nokeepalive directive disabling keepalive.  However the environment variable in perl still reports
HTTP_CONNECTION = Keep-Alive

I don't believe this should be happening.
>How-To-Repeat:
Set the conf file as described above
>Fix:
no
>Release-Note:
>Audit-Trail:

From: "Jason" <jter@cartmanager.net>
To: <submit@bugz.apache.org>, <apache-bugdb@apache.org>
Cc:  
Subject: Re: mod_setenvif/9224: nokeepalive doesn't properly change the HTTP_CONNECTION env variable
Date: Fri, 21 Dec 2001 11:17:34 -0700

 I found out more problems with setenvif
 
 
 
 If I use
 SetEnvIf User-Agent ".*MSIE.*"  "nokeepalive" "ssl-unclean-shutdown" "downgrade-1.0" "force-response-1.0"
 It stores the ENV properly
 
 If I use
 SetEnvIf User-Agent ".*MSIE.*"  nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
 Then all periods seem to be converted into underscores somehow.
 
 And inside of mod_perl dashes are also converted into underscores in %ENV.
 
 ----- Original Message ----- 
 From: <submit@bugz.apache.org>
 To: <jter@cartmanager.net>
 Sent: Friday, December 21, 2001 10:50 AM
 Subject: Re: mod_setenvif/9224: nokeepalive doesn't properly change the HTTP_CONNECTION env variable
 
 
 > Thank you very much for your problem report.
 > It has the internal identification `mod_setenvif/9224'.
 > The individual assigned to look at your
 > report is: apache. 
 > 
 > >Category:       mod_setenvif
 > >Responsible:    apache
 > >Synopsis:       nokeepalive doesn't properly change the HTTP_CONNECTION env variable
 > >Arrival-Date:   Fri Dec 21 09:50:00 PST 2001
 
State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Fri Dec 21 10:32:43 PST 2001
State-Changed-Why:
HTTP_* environment variables are what the client sends.  They have nothing to do with how the server is responding.  So it is completely correct for the HTTP_* variables to be the same even if the server is deciding to respond differently.

And yes, environment variables passed to CGIs, mod_perl, etc. are converted based on the rules in the CGI spec which does change things to _, etc.
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]