Emblems are served as MIME=text/html rather than image/*

Bug #808284 reported by Paul Sladen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Confirmed
Low
Unassigned

Bug Description

An emblem such as:

  https://launchpadlibrarian.net/1013640/ubuntu_emblem.png

is served with content type 'text/html'. Ideally this should be 'image/*' ('image/png') in the case of the above.

Tags: librarian
Revision history for this message
Martin Pool (mbp) wrote :

I've seen this too. I wonder if it's just that some were injected into the librarian with the wrong type, or if it affects all icons.

Changed in launchpad:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Martin Pool (mbp) wrote :

This has similar symptoms to bug 703807, but it's different. That bug is to do with files being marked text/html only when fetched through banana, but in this case the files are consistently text/html whichever front end proxy is used.

It might be interesting to see if the librarian internally thinks they're text/html or not.

tags: added: librarian
Revision history for this message
Martin Pool (mbp) wrote :

The libraryfilealias for https://launchpadlibrarian.net/1013640/ubuntu_emblem.png says it's image/png.

Revision history for this message
William Grant (wgrant) wrote :

This is a dupe. Both frontends sometimes return the bad data, sometimes not.

Revision history for this message
Paul Sladen (sladen) wrote :

wgrant: the symptoms might be the same, but I'm not convinced that the cause is the same. In this case, the wrong MIME type does not appear to vary as a function of the front-end cache it is served via; it is, AFAICT, always being served text/html.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 808284] Re: Emblems are served as MIME=text/html rather than image/*

On Tue, Jul 12, 2011 at 8:47 PM, Paul Sladen <email address hidden> wrote:
> *** This bug is a duplicate of bug 703807 ***
>    https://bugs.launchpad.net/bugs/703807
>
> wgrant: the symptoms might be the same, but I'm not convinced that the
> cause is the same.  In this case, the wrong MIME type does not appear to
> vary as a function of the front-end cache it is served via; it is,
> AFAICT, always being served text/html.

The front end doesn't affect it - that was confusion and incorrect.

The fault is a twisted bug with IMS requests.

Revision history for this message
William Grant (wgrant) wrote :

Well, we were seeing good results from one frontend occasionally, presumably when the content had expired from the cache and been reloaded with a 200.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.