Bug 31782

Summary:

HTML5 audio tag request happens twice

Product:

WebKit

Reporter:

kain <masterkain>

Component:

Media

Assignee:

Nobody <webkit-unassigned>

Status:

UNCONFIRMED

Severity:

Normal

CC:

ahmad.saleem792, destra, eric.carlson, jer.noble, nicholas.young

Priority:

Version:

528+ (Nightly build)

Hardware:

Mac (Intel)

OS:

OS X 10.6

Attachments:

Description	Flags
Packet Dump	none
Packet Dump - Round 2	none

kain

Reported 2009-11-22 00:28:32 PST

I was trying to nail down a problem I'm having with Safari 4 on Snow Leopard, when using the <audio> tag a request is issued to the src server, but it does happen twice. This problem got my attention because we pay per hit on the remote storage where we keep files.

Attachments
Packet Dump (4.69 KB, text/plain) 2010-02-14 20:20 PST, Nick Young	no flags	Details
Packet Dump - Round 2 (13.28 KB, text/plain) 2010-02-14 20:27 PST, Nick Young	no flags	Details
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.

Eric Carlson

Comment 1 2009-11-25 11:20:57 PST

A test case is needed here - does this happen with every <audio> element or does it depend on the content type; does it happen with <video> as well, etc.

kain

Comment 2 2009-11-25 15:55:18 PST

(In reply to comment #1) > A test case is needed here - does this happen with every <audio> element or > does it depend on the content type; does it happen with <video> as well, etc. hi Eric, I'm on a tight schedule, will post back a test case and some other findings soon. thanks for the attention.

kain

Comment 3 2009-12-02 11:45:28 PST

after conducting other tests the same behaviour can be observed even with the video tag. steps to reproduce are simple: consult the log file of an http server and use the server address as src, upon page load webkit will call src twice, sometimes even three times. it doesn't matter what media is being played.

Nick Young

Comment 4 2010-02-14 19:36:52 PST

Actually, I've observed this too. The multiple requests are issued by the CoreMedia User Agent. In my case - User-Agent: Apple Mac OS X v10.6.2 CoreMedia v1.0.0.10C540. Each request has a different "Range" header, and each request is on a different (sequential, consecutive) port. Looks like parallel/progressive downloading to me :) I have a packet dump here, will provide on request.

Eric Carlson

Comment 5 2010-02-14 20:15:59 PST

(In reply to comment #4) > > I have a packet dump here, will provide on request. That would be very helpful, thanks!

Nick Young

Comment 6 2010-02-14 20:20:56 PST

Created attachment 48739 [details] Packet Dump Generated with Wireshark. Hopefully there isn't anything personally identifiable in the cookies, etc. If there is, keep it to yourself ;)

Nick Young

Comment 7 2010-02-14 20:27:07 PST

Created attachment 48740 [details] Packet Dump - Round 2 Whoops. I was a little overzealous when filtering out those packets. Here's the extended version ;)

Ahmad Saleem

Comment 8 2023-10-15 06:50:04 PDT

There are some stackoverflow post (but old) with mention of this issue but unable to find recent one. Is this still applicable?

Note You need to log in before you can comment on or make changes to this bug.