On Jan 28, 2011, at 1:41 AM, sree_at_work_at_yahoo.com wrote:
> Hi Paul/Pavel,
>
> As per the media types spec, it seems the 'space' is recommended after
> the 'type/subtype;' and before 'param=value'
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17
> search for section 5.1.1 at http://www.ietf.org/rfc/rfc2046.txt
>
The specs do not recommend such use, the white spaces in the examples
are for human readability. However, if i ever wrote an
interoperability RFC i would certainly recommend the use :-)
The problem is parsing implementations not conforming to the correct
grammar and being too restrictive. I suspect at some point there was
some copy and pasting of code then systems were deployed that could
not be changed and newer client code written needed to interoperate.
Thanks,
Paul.
> MediaTypeProvider.toString()
> Line #66, is not appending/preserving this 'space' in question.
>
> Do you want me to open a bug for this ?
>
> Thanking you.
>
> With Regards
> Sree