[Webkit-unassigned] [Bug 105741] Make HTTP Accept header for images useful without slowing down page load speeds and without using excessive bandwidth.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=105741


Brady Eidson <beidson at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Make HTTP Accept header for |Make HTTP Accept header for
                   |images useful               |images useful without
                   |                            |slowing down page load
                   |                            |speeds and without using
                   |                            |excessive bandwidth.




--- Comment #2 from Brady Eidson <beidson at apple.com>  2012-12-27 17:49:34 PST ---
(In reply to comment #0)
> It's been suggested elsewhere [2] that the current HTTP Accept header for images (*/*) in Chrome and Safari is useless when it comes to server-driven negociation.

>From the article:
"Chrome and Safari headers are effectively useless - we accept everything!"

At least in Safari's case we accept everything because...  well... we support everything that can be opened on the system.

"Opera is the only one explicitly enumerating the supported filetypes, which is the behavior we want..."

...And the list of types Opera claims to support is much smaller than the list of types Safari on Mac actually supports.

If we were to actually enumerate all types we actually support we'd have request headers much, much larger than average and slow down page loads.

I've retitled the bug to:
"Make HTTP Accept header for images useful without slowing down page load speeds and without using excessive bandwidth"
...to specify what an acceptable resolution to it would be.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.