JDK-6611381 : Add cookie and proxy support for 1.4.2
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u5,6u10,6u13
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2007-09-30
  • Updated: 2010-04-04
  • Resolved: 2008-12-27
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Relates :  
When the new plugin is running on 1.4.2 its cookie handling support will not work, since it relies on APIs introduced in 5.0. A forward port of the 1.4.2 plugin's cookie-related code to the new plugin will be needed. This code will be used when the new plugin is running an applet on a 1.4.2 JRE.
While making the 1.4.2 support work in the new plug-in it was also discovered that the proxy support also will not work as it is based around the java.net.ProxySelector API which was introduced in 1.5. Whatever mechanism was used in 1.4.2 will need to be forward ported to make this work.
It was also determined that the DeployCacheHandler mechanism doesn't work on 1.4.2 since it relies on the java.net.ResponseCache which was introduced in 1.5. It is unclear whether this needs to be supported on 1.4.2; we believe this only handles caching of arbitrary data the user downloads via URLConnection manually, which is useful but not critical.

EVALUATION With 1.4.2 having reached its end of life there are no resources available to make this work. Closing as Will Not Fix.

EVALUATION This isn't a showstopper for 6u10. Decommitting from 6u10 and recommitting to 6u12.

EVALUATION At this time fixing these issues is not as important as other work. Lowering the priority to a P4.