On Oct 26, 9:01 am, Alexander Kiel <[email protected]> wrote: > Hi, > > I'm currently working on a application which uses custom XML media > types. I use firebug to debug the network traffic between the browser > and the server. > > If I have a response with Content-Type header application/xml, firebug > will show the response as text in the response tab and as nicely > formatted XML in a separate XML tab. > > But if I have a response with Content-Type header application/atom+xml > or something in the scheme application/*+xml, firebug will print "The > resource from this URL is not text: <URL>". In order to safe memory Firebug doesn't cache all responses (e.g. binary), but only those that have specific mimeType. You can use "extensions.firebug.cache.mimeTypes" preference (about:config) to extend/customize the built in list (the pref can contain list of additional mime type to cache separated by a space).
> You can test that withhttp://www.alexanderkiel.net/feed/atom/. Yes, I did and there this doesn't work even if I specify additional mime type using the pref mentioned above. Please report a bug for this. http://code.google.com/p/fbug/issues/list?start=0 > RFC 3023 [1] defines the suffix '+xml' for all XML-based media types. > So firebug could render all media types */*+xml as XML. So, far the built in list of mime types is trying to list all 'xml' mime types, but using a regular expression could be better. You can file a separate bug report for this. Thanks! Honza -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
