Re: [pkix] CertImage: SVGZ in data: URI

James,

I asked Yngve Pettersen from Opera how they would treat a data URL with
image/svg+xml containing svgz. He confirmed that this works just fine.

/Stefan

On 10-02-18 1:50 PM, "Manger, James H" <James.H.Manger@team.telstra.com>
wrote:

> Stefan,
> 
> The certimage-06 now makes it absolutely clear how SVGZ must be supported.
> That is great.
> 
> It might mean a little bit of SVG-specific code needs to appear in an
> otherwise generic "data URI"/"media type" block of code - but that's a very
> minor quibble.
> If someone has tried a data URI with SVG and with SVGZ in an existing tool
> that supports both, that would be ideal. Perhaps in an Opera browser?
> 
> My concern is resolved.
> 
> --
> James Manger
> 
> ________________________________________
> From: Stefan Santesson [stefan@aaa-sec.com]
> Sent: 18 February 2010 22:51
> To: Stefan Santesson; Manger, James H; pkix
> Subject: Re: [pkix] CertImage: SVGZ in data: URI
> 
> James,
> 
> I have now submitted an update:
> 
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-pkix-certimage-06.txt
> 
> Does this resolve your concerns?
> 
> /Stefan
> 
> On 10-02-18 10:59 AM, "Stefan Santesson" <stefan@aaa-sec.com> wrote:
> 
> James,
> 
> The differentiation in content encoding given by the file extension .svg or
> .svgz is, as you point out, lost when providing the image in a ³data:² URI.
> Image/svg+xml is however a valid mediatype for both svg and svgz encoded
> content and thus I see nothing wrong in including compressed svgz data under
> that media type.
> 
> See for example: http://wiki.svg.org/MIME_Type
> 
> I agree with you that the text in the draft should be more specific about this
> and explicitly allow both svg and svgz under image/svg+xml with added
> reference to SVG 1.1 section 1.2 and RFC 1952 (GZIP). I would also hate to
> loose the compression.
> 
> I¹ll do some updates and resubmit.
> 
> /Stefan
> 
> 
> On 10-02-18 5:28 AM, "Manger, James H" <James.H.Manger@team.telstra.com>
> wrote:
> 
> Stefan,
> 
> Does a ³data:² URI with a gzipped SVG work (SVGZ instead of SVG)  as in the
> example in appendix A?
> There is nowhere in a ³data:² URI [RFC2397] to indicate the Content-Encoding.
> The only way to parse it is to use heuristics to guess if the content is SVG
> or SVGZ.
> The heuristic is easy (a GZIP value starts with 2 magic bytes 1F 8B), but I
> don¹t know if tools commonly do this.
> Perhaps the certimage spec needs to explicitly say that SVG and SVGZ are valid
> in a data URI that lists the image/svg+xml media type. It would be a shame to
> lose the compression (x5.6 in the example).
> 
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix