https://issues.apache.org/bugzilla/show_bug.cgi?id=53814
Konstantin Kolinko <knst.koli...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #3 from Konstantin Kolinko <knst.koli...@gmail.com> ---
One small difference is
7.0.26:
Content-Type: multipart/byteranges; boundary=CATALINA_MIME_BOUNDARY
7.0.30:
Content-Type: multipart/byteranges;boundary=CATALINA_MIME_BOUNDARY
There is no whitespace in ";boundary". (See bug 52811 for a cause of this
change).
----------
Well, the grammar is (RFC 2616)
media-type = type "/" subtype *( ";" parameter )
parameter = attribute "=" value
or (RFC 2045)
content := "Content-Type" ":" type "/" subtype
*(";" parameter)
; Matching of media type and subtype
; is ALWAYS case-insensitive.
parameter := attribute "=" value
so officially there is no need for a whitespace there.
If Adobe Reader indeed expects a '; ', then they are not following the
specification.
I note, though, that many (if not all) examples in the specification have a
whitespace before parameter. It seems that it would be more fool-proof to
always include a whitespace there.
See o.a.tomcat.util.http.parser.AstMediaType#toString(), #toStringNoCharset()
s/sb.append(';');/sb.append("; ");/
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
