You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://httpwg.org/specs/rfc9110.html#status.3xx -
When automatically following a redirected request, the user agent SHOULD resend the original request message with the following modifications:
Replace the target URI with the URI referenced by the redirection response's [Location](https://httpwg.org/specs/rfc9110.html#field.location) header field value after resolving it relative to the original request's target URI.
Remove header fields that were automatically generated by the implementation, replacing them with updated values as appropriate to the new request. This includes:
Connection-specific header fields (see Section 7.6.1),
Header fields specific to the client's proxy configuration, including (but not limited to) Proxy-Authorization,
Origin-specific header fields (if any), including (but not limited to) Host,
Validating header fields that were added by the implementation's cache (e.g., If-None-Match, If-Modified-Since), and
Resource-specific header fields, including (but not limited to) Referer,
Origin, Authorization,
and Cookie.
In v2.40 I see that the original jersey request is used with just a change to the URI causing the original Authorization header to be resent.
https://httpwg.org/specs/rfc9110.html#status.3xx -
When automatically following a redirected request, the user agent SHOULD resend the original request message with the following modifications:
Remove header fields that were automatically generated by the implementation, replacing them with updated values as appropriate to the new request. This includes:
Connection-specific header fields (see Section 7.6.1),
Header fields specific to the client's proxy configuration, including (but not limited to)
Proxy-Authorization,
Origin-specific header fields (if any), including (but not limited to)
Host,
Validating header fields that were added by the implementation's cache (e.g.,
If-None-Match,
If-Modified-Since), and
Resource-specific header fields, including (but not limited to)
Referer,
Origin,
Authorization,
and Cookie.
In v2.40 I see that the original jersey request is used with just a change to the URI causing the original Authorization header to be resent.
Logs from my test
Initial request
POST /ic/api/integration/v1/archive HTTP/1.1
Authorization: userwelcome1
User-Agent: oracle-cloud-rest/23.3.1
Content-Type: multipart/form-data;boundary=Boundary_21_715846865_1694630297154
Accept-Encoding: gzip
host:
transfer-encoding: chunked
DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 302 Found
location: https:///ic/api/integration/v1/postFinal
access-control-allow-origin: *
...
}
nioEventLoopGroup-22-10 ts = 1694630298219 writeAndFlush(nettyRequest) - DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
POST /ic/api/integration/v1/postFinal HTTP/1.1
Authorization: userwelcome1
User-Agent: oracle-cloud-rest/23.3.1
Content-Type: multipart/form-data;boundary=Boundary_21_715846865_1694630297154
Accept-Encoding: gzip
MIME-Version: 1.0
host:
transfer-encoding: chunked
The text was updated successfully, but these errors were encountered: