https://bugs.openjdk.org/browse/JDK-8294196

[Jaikiran Pai]

I've assigned that issue to myself. I haven't checked the latest state 
of some of the (draft) RFCs linked in this discussion. I will do so in 
the coming days.

-Jaikiran

On 08/06/25 8:53 pm, Julian Reschke wrote:
> On 09.01.2025 15:30, Julian Reschke wrote:
>> Hi there.
>>
>> I'd like to get back to the topic
>>
>> "Investigate introducing an API on the HttpClient which allows
>> applications to get access to "interim" HTTP responses" --
>> https://bugs.openjdk.org/browse/JDK-8294196
>>
>> To avoid confusion: the *bugs* with respect to handling 1xx responses
>> have been thankfully fixed (see
>> https://github.com/openjdk/jdk/pull/10229 and
>> https://github.com/openjdk/jdk/pull/10169).
>>
>> What's still missing is a way to actually inspect the contents of the
>> 1xx messages while waiting for a final response (status >= 200). That
>> could be a callback that provides the status code and the response
>> header fiels when 1xx messages are received.
>>
>> This would be useful when processing 103 messages (Early Hints - RFC
>> 8297) or 104 messages (Upload Resumption Supported - used for
>> "draft-ietf-httpbis-resumable-upload").
>>
>> Use cases are summarized over here:
>>
>>   https://github.com/greenbytes/java-http-1xx-tests
>>
>> (tests live here as well).
>>
>> Let me know if more information is needed.
>>
>> Best regards, Julian
>
> Ping. What is the best way to get this considered? I was asked to 
> document use cases, and I think I did. Is there anything missing? I'll 
> happily expand that section if needed...
>
> Best regards, Julian