-
Enhancement
-
Resolution: Duplicate
-
P3
-
None
-
1.3.0, 1.3.1, 5.0
-
generic, x86
-
generic, windows_nt, windows_2000
Name: ca25432 Date: 06/11/2002
This feature will benefit any application that must send large quantities
of data via HTTP POSTs. Some developers have switched to using third-party HTTP
client implementations for applications (e.g., WebDAV)
Internet Printing Protocol (IPP) is also slated for Tiger (RFE 4641868). IPP is
based upon HTTP and sends print requests (which can be very large) via HTTP
POSTs and would benefit from this feature
The feature does not require any API changes.
======================================================================
In technical terms the above translates to :-
1. When the content-length is known in advance it can be set in
the http request headers and the entity body can be streamed to
the server.
2. When the content-length is not known in advance, but we know
that the server is a HTTP 1.1 server, then the entity body can
be chunked encoded.
See also 4635350 and 4363479.
###@###.### 2002-10-30
This feature will benefit any application that must send large quantities
of data via HTTP POSTs. Some developers have switched to using third-party HTTP
client implementations for applications (e.g., WebDAV)
Internet Printing Protocol (IPP) is also slated for Tiger (RFE 4641868). IPP is
based upon HTTP and sends print requests (which can be very large) via HTTP
POSTs and would benefit from this feature
The feature does not require any API changes.
======================================================================
In technical terms the above translates to :-
1. When the content-length is known in advance it can be set in
the http request headers and the entity body can be streamed to
the server.
2. When the content-length is not known in advance, but we know
that the server is a HTTP 1.1 server, then the entity body can
be chunked encoded.
See also 4635350 and 4363479.
###@###.### 2002-10-30
- duplicates
-
JDK-4363479 support http 1.1 chunked encoding output
- Closed
-
JDK-4635350 HTTP POST writes should be flushed when Content Length is set
- Closed
-
JDK-5026745 Cannot flush output stream when writing to an HttpUrlConnection
- Resolved