JDK-4676386 : better user-agent value in http request header
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.2.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-04-29
  • Updated: 2002-11-19
  • Resolved: 2002-11-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 Availability Release.

To download the current JDK release, click here.
Other
1.4.2 mantisFixed
Description
request from JSR 124:

According to the HTTP 1.1 spec the User-Agent header should be a 
sequence of product tokens (defined in section 3.8) and comments 
(surrounded by parentheses - see section 2.2).  So how about making it:

User-Agent: javaws/1.2-beta (internal) J2SE/1.3.1

The comment (in parentheses) could be anything.

Maybe we should consider using the header primarily to indicate the 
standards supported, and only secondarily, if at all, the product.  E.g.

User-Agent: JNLP/1.2 javaws/1.2-beta (internal) J2SE/1.3.1
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b08
31-08-2004
EVALUATION this should be very easy to fix. we should fix it for hopper. ###@###.### 2002-04-29
29-04-2002