Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 20
Affects Version/s: 11, 17, 19
Component/s: core-libs
Labels:

Subcomponent:
java.net
Resolved In Build:
b17
Verification:
Verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8337732	17.0.13	Matthias Baesken	P3	Resolved	Fixed	b02
JDK-8338120	11.0.25	Matthias Baesken	P3	Resolved	Fixed	b03

When the HttpClient receives a response with 102 or 103 it simply returns that response to the caller and considers the exchange done. This leaves the caller in a bind as it can't receive the final 200 response.

A minimal fix (backportable) would be to ignore the 102 or 103 response and wait for the final 200 response.

For the mainline we should probably add a new no-op method with an empty default body to the BodyHandler interface to give the caller a chance to intercept the 1xx response.

backported by

JDK-8337732 HttpClient doesn't handle 102 or 103 properly

Resolved

JDK-8338120 HttpClient doesn't handle 102 or 103 properly

Resolved

duplicates

JDK-8293574 HttpClient mishandles HTTP 1xx status codes as final response messages

Closed

relates to

JDK-8170305 URLConnection doesn't handle HTTP/1.1 1xx (informational) messages

Closed

JDK-8294196 Investigate introducing an API on the HttpClient which allows applications to get access to "interim" HTTP responses

Open

links to

Commit openjdk/jdk/800e68d6

Commit(master) openjdk/jdk11u-dev/73dc9e89

Commit(master) openjdk/jdk17u-dev/10000286

Review openjdk/jdk/10169

Review(master) openjdk/jdk11u-dev/2896

Review(master) openjdk/jdk17u-dev/2753

(6 links to)

Assignee:: Jaikiran Pai

Reporter:: Daniel Fuchs

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 2022-08-08 06:13

Updated:: 2024-08-09 07:09

Resolved:: 2022-09-22 02:20

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates