[jira] Updated: (HTTPCORE-124) application-controlled HeaderValueParser

["Roland Weber (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HTTPCORE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roland Weber updated HTTPCORE-124:
----------------------------------

    Attachment: 2k7-11-04-hdr-parser-2.txt

Here is another take on this problem: Header.getElements() is gone altogether.
The header value parser is now an argument of the BasicHeaderElementIterator.
Other places calling Header.getElements() have been changed to use the default parser (for now).
The LaxContentLengthStrategy should rather use a token iterator, when we have one.

There is a semantic difference in the handling of headers with null value.
Previously, these were mapped to an empty element list in Header.getElements().
I believe that is not correct, but that's something we can figure out in the beta phase.

cheers,
  Roland


> application-controlled HeaderValueParser
> ----------------------------------------
>
>                 Key: HTTPCORE-124
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-124
>             Project: HttpComponents Core
>          Issue Type: Improvement
>    Affects Versions: 4.0-alpha6
>            Reporter: Roland Weber
>            Assignee: Roland Weber
>            Priority: Trivial
>             Fix For: 4.0-beta1
>
>         Attachments: 2k7-10-14-hdr-parser.txt, 2k7-11-04-hdr-parser-2.txt
>
>
> As briefly mentioned elsewhere, it would be consistent if the header value parser can be set on all headers, not just on BufferedHeader.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org