hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Johnson <sjohn...@mercury.com>
Subject RE: HTTPClient 3.0 vs 2.0 questions
Date Thu, 24 Mar 2005 23:59:55 GMT
Hi Oleg,

This is exactly the information requested.

Thanks for your time and expertise, 

Steve Johnson, Software Engineer, sjohnson@mercury.com
direct 720.564.6532 
www.mercury.com 

 
 
www.mercury.com 

-----Original Message-----
From: Oleg Kalnichevski [mailto:olegk@apache.org] 
Sent: Thursday, March 24, 2005 4:43 PM
To: HttpClient Project
Cc: sjohnson@mercury.com
Subject: Re: HTTPClient 3.0 vs 2.0 questions

Hi Steve,

HttpClient 3.0 will certainly choke on an extra status line, because it
does not represent a valid header. HttpClient will log a warning and
discard a malformed cookie or an authentication challenge, as long as it
represents a valid header

Hope this helps

Oleg

On Thu, 2005-03-24 at 13:21 -0800, Steve Johnson wrote:
> Hi All,
> 
>  
> 
> If anyone knows without looking it up:
> 
>  
> 
> Will 3.0 ignore multiple status lines in response headers? The status line is first,
but there are others
> sprinkled in the response headers.
> 
> In general, will 3.0 silently log or ignore unrecognized headers? An example is a Set-Cookie:
domain=bob;
> path=/, which has no name=value pairs.
> 
> Another example is any line in the response headers without a colon.
> 
>  
> 
> Thanks for your time,
> 
>  
> 
> Steve Johnson, Software Engineer, sjohnson@mercury.com
> 
> direct 720.564.6532 
> 
> www.mercury.com <http://www.mercury.com/>  
> 
>  <http://www.mercury.com/> 
> 
>  <http://www.mercury.com/>  
> 
>  
> 
> 
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message