Community
Participate
Working Groups
With followRedirects set to true, 308 redirects are not followed (e.g. if git server is behind the nip.io service) Looks like this block: case HttpConnection.HTTP_MOVED_PERM: case HttpConnection.HTTP_MOVED_TEMP: case HttpConnection.HTTP_SEE_OTHER: case HttpConnection.HTTP_11_MOVED_TEMP: in org.eclipse.jgit.transport.TransportHttp.connect should include the 308 code and it does not.
*** Bug 560935 has been marked as a duplicate of this bug. ***
New Gerrit change created: https://git.eclipse.org/r/159094
Gerrit change https://git.eclipse.org/r/159094 was merged to [master]. Commit: http://git.eclipse.org/c/jgit/jgit.git/commit/?id=04e16afb05912f3a163d8cda3560a5b2f1ea997f
Will be fixed in JGit 5.8.0, scheduled for June 2020. Please note https://tools.ietf.org/html/rfc7538#section-4 : Thus, servers will not be able to rely on automatic redirection happening similar to status codes 301, 302, or 307. Therefore, the use of status code 308 is restricted to cases where the server has sufficient confidence in the client's understanding the new code or when a fallback to the semantics of status code 300 is not problematic. JGit doesn't handle response code 300 Multiple Choices.