hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HTTPCLIENT-688) HttpOptions.getAllowedMethods expects single Allow header
Date Wed, 14 Nov 2007 17:03:43 GMT

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

Oleg Kalnichevski resolved HTTPCLIENT-688.

    Resolution: Fixed

Patch checked in. I just made a minor change to it and replaced the array of Headers with
our new shiny HeaderIterator. Many thanks for contributing the patch, Adrea


> HttpOptions.getAllowedMethods expects single Allow header
> ---------------------------------------------------------
>                 Key: HTTPCLIENT-688
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-688
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient
>    Affects Versions: 4.0 Alpha 1
>            Reporter: Roland Weber
>            Priority: Trivial
>             Fix For: 4.0 Alpha 3
>         Attachments: fix_httpc_688.patch
> In client.methods.HttpOptions.getAllowMethods(), a single Allow header is parsed to obtain
the result. Since the value is a comma-separated list, servers can optionally return the values
in multiple headers. HttpMethod.getHeaders(name) should be used instead of .getFirstHeader(name).

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

View raw message