commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12244] New: - Response Header ordering not preserved from the server
Date Tue, 03 Sep 2002 01:48:00 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12244>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12244

Response Header ordering not preserved from the server

           Summary: Response Header ordering not preserved from the server
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: HttpClient
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: jsdever@sympatico.ca


The headers are not returned by getResponseHeaders() in the order
that they are read from the stream.  The headers are stored in a HashMap and are
effectively just the values() which are in no particular order.

We could use a Vector in place of a HashMap for the headers so that
the order is preserved, but would have abstract away the lookups by the name
field (which there are many).  Alternatively, we could mirror the contents in
the hashmap in a vector (or array) so that we still have fast and convienent
lookups, but still have order preservation of the headers.

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message