JDK-8007315 : HttpURLConnection.filterHeaderField method returns null where empty string is expected
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 7u4
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-01-31
  • Updated: 2013-08-16
  • Resolved: 2013-02-19
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 Availabitlity Release.

To download the current JDK release, click here.
JDK 7 JDK 8
7u40Fixed 8 b82Fixed
Description
SHORT SUMMARY: NPE seen in HttpSOAPConnection.post method
INDICATORS: 
NPE occurring in 
com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post
when run through a plugin/webstart environment.
COUNTER INDICATORS:
TRIGGERS:
Presense of only HttpOnly headers in the Set-Cookie headers value which 
results in a
null value being passed to calling code in plugin environment.
KNOWN WORKAROUND:
N/A
PRESENT SINCE:
7u4 (https://jbs.oracle.com/bugs/browse/JDK-7095980)
HOW TO VERIFY:
Will write a regression testcase.
NOTES FOR SE:
REGRESSION: Y
 

Comments
HttpOnly.java passes
2013-08-16

Suggested fix is to modify HttpURLConnection.filterHeaderField method so that "" <empty string> instead of null is returned when an empty set of field values is arrived at after filtering out the necessary fields.
2013-01-31

There isn't enough information here to know if this bug should be in core-libs/java.net or xml/jax-ws.
2013-01-31