[
https://issues.apache.org/jira/browse/HTTPCLIENT-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650428#comment-16650428
]
David Peleg commented on HTTPCLIENT-1946:
-----------------------------------------
Hi Gary and thanks for the response.
My own concern is not that big, since I can check the response code and
implement the redirect logic myself, in my application.
My concern is that an RFC which is 3.5 years old has no implementation other
than a beta unreleased version.
Since Apache HTTP client is a very popular and widely spread, not only by
itself but also embedded inside other products as a library, and since the fix
is very local and simple, as much as I can see (2-3 lines of code + some
tests), and since the consequences might be disturbing and sometimes might also
break existing redirect-logic of existing products, I am asking again, why not
consider fixing existing versions as well, at least 4.x branch which is not EOL?
Or is there a way to ask the community via votes?
> 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), 4.5.6
> Environment: Irrelevant
> Reporter: David Peleg
> Priority: Major
> Labels: easyfix, usability
>
> 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() (in version 3.x) 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]
