JDK-8203850 : java.net.http HTTP client should allow specifying Origin and Referer headers
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 10,11
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-05-25
- Updated: 2018-10-19
- Resolved: 2018-10-12
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 11 | JDK 12 |
|---|---|
| 11.0.2Fixed | 12 b16Fixed  |
Related Reports
|
Blocks :
|
Description
A DESCRIPTION OF THE PROBLEM : Apparenty, those headers are forbidden in HTTP client because XMLHttpRequest API forbids those. (https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_header_name). XMLHttpRequest API forbids those, as allowing them would make Cross-origin resource sharing API insecure. This isn't an issue for Java HTTP client, as it doesn't implement CORS, and due to not being a web browser likely never will. This is useful, as some websites require those headers to work.
Comments
|