Wednesday, September 21, 2011

[YouTube-API] Sniffing YouTube-API controls (with wireshark)

Hi @all,

I am currently working on my bachelor thesis: I want to analyze the
packet stream of YouTube-Videos with wireshark. I can see the various
requests on the beginning and I can also follow the TCP stream of the
video, containing the video-header (encoded in AMF), but now I'm
stuck:

I want to identify the packets, where the user sends a feedback to
YouTube - that means, e.g., playing Pause/Start. I also want to
identify the packets, where YouTube itself realizes it's gonna stall
the video. So the problem is, to find that information in the packet
stream without using the YouTube-API itself!

I've tried to spot the packets, but I am not sure about the results.
It seems like there are only some HTTP answers from YouTube with
status 204 No Content - but I don't know if that's a respond to
pressing Pause.. Can anyone help me?

(I do know that YouTube will open a new TCP connection if the user
jumps to a part of the video which hasn't streamed yet.)

At least I guess I've found the packet, where I pressed play again
(because that should be the packets where a new GET request gets
sent?):

GET: Request URI [truncated]: /s?
sd=B4A7DDA24HH1316609848492094&nsivbblmax=184767.000&plid=AAStcx412R5h-
naI&hcbd=1175016&nsivbblc=59&hcbt=1.7&bd=3863120&h=360&sourceid=y&nsiabblc=59&bt=8.512&sdetail=f
%3Atopvideos_music%2Cp%3A%2F&cfps=23.9234449

Best regards,
Dave

--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.

No comments:

Post a Comment