[
https://issues.apache.org/jira/browse/HTTPCLIENT-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650353#comment-16650353
]
David Peleg commented on HTTPCLIENT-1946:
-----------------------------------------
Hi Gary.
First of all, servers around the world are indeed using this response code. The
RFC is from April 2015. It's about 3.5 years since then, now.
And branch 3.x is still widely used, sometimes embedded in other third party
products.
So for the reputation of Apache HTTP client, I think it's better to fix it.
However, if "end of life" means there are no fixes anyway, any more, why not
let the open community handle 3.x branch under GitHub?
Anyway, I also looked at the latest 4.x branch (4.5.6) and surprisingly I see
that even there it's not fixed. 308 is never mentioned or handled as an HTTP
redirect response code.
Maybe I need to add this version as well.
So we're in situation that Apache HTTP client doesn't handle 308 codes, even
though servers are using it.
And the fix seems to me very easy.
So what do you suggest?
What is the best way to go from here?
> Support relatively new HTTP 308 redirect - RFC7538
> --------------------------------------------------
>
> Key: HTTPCLIENT-1946
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1946
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 3.1 (end of life)
> Environment: Irrelevant
> Reporter: David Peleg
> Priority: Major
> Labels: easyfix, usability
> Fix For: 3.1 (end of life)
>
>
> RFC7538 added a new HTTP redirect code: 308.
>
> To support it all you need is adding 2 rows:
> # In HttpStatus add constant: SC_PERMANENT_REDIRECT = 308
> # In HttpMethodDirector.isRedirectNeeded() add SC_PERMANENT_REDIRECT to the
> switch clause.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
