Winamp streaming through Fiddler as proxy?

[romor]

I've set Fiddler as 127.0.0.1:8888 proxy while trying to play Internet
radio playlist and I just can't make it work :(

I read couple of discussions saying that streaming button should be
turned on, but without success.

I also tried adding:
var bBufferResponse: boolean = false;
to sampleruls.js where was suggested in Fiddler help, but still
nothing

Winamp reports timeout or something similar also Video Lan Player
reports bad request - error 500 (I can't remember exact errors)

Thanks

[EricLaw]

Without exact information, I really can't help you.

But first, a more important question: What are you hoping to use
Fiddler for?

[romor]

I have many plugins/components for winamp, vlc, foobar... that are
accessing internet. I use Fiddler for tracking down responses from
them, and also I'm scripting a little...

I can play these streams without Fiddler proxy, or course, but as I
set Fiddler by default, if I want to play some stream I need to
disable proxy. Now I want to circumvent this behavior

Thanks

[romor]

About the error: When I hit play for a stream in my player, than this
is one error example:

Unable to open item for playback (Fiddler - Bad Response (500)):
"http://streamer-dtc-aa01.somafm.com/stream/1032"


This is from session properties (just to mention I've set
bBufferResponse to false and didn't click on streaming button):

SESSION STATE: Aborted.

Response Entity Size: 32346 bytes.

== FLAGS ==================
X-PROCESSINFO: foobar2000:4360
X-HTTPPROTOCOL-VIOLATION: [HTTP Protocol Violation] Response does not
start with HTTP. Data:

200 OK
X-CLIENTPORT: 49455
X-TRANSFER-SIZE: 32346
X-EGRESSPORT: 49456
X-TTLB: 1.235
X-CLIENTIP: 127.0.0.1
X-HOSTIP: 205.188.234.1
X-TTFB: 1.156

== TIMING INFO ============
ClientConnected: 23:19:20:1904
ClientDoneRequest: 23:19:20:1904
Gateway Determination: 0ms
DNS Lookup: 1110ms
TCP/IP Connect: 3359ms
ServerGotRequest: 23:19:24:6777
ServerBeginResponse: 23:19:25:8339
ServerDoneResponse: 23:19:25:9101
ClientBeginResponse: 23:19:25:9101
ClientDoneResponse: 23:19:25:9101

Overall Elapsed: 00:00:05.7197266

The response was buffered before delivery to the client.

== WININET CACHE INFO ============
This URL is not present in the WinINET cache. [Code: 2]
* Note: The above represents WinINET's ~current~ cache state, not the
state at the time of the request.


Without bBufferResponse, but with streaming button checked the player
just don't react - it says "loading file..." and stays that way until
I press stop. And this is from session properties in this case:

SESSION STATE: ReadingResponse.
DOWNLOAD PROGRESS: 1.533.561 bytes.



== FLAGS ==================
X-PROCESSINFO: foobar2000:4360
X-CLIENTIP: 127.0.0.1
X-HTTPPROTOCOL-VIOLATION: [HTTP Protocol Violation] Response does not
start with HTTP. Data:

200 OK[HTTP Protocol Violation] Protocol violation. No Connection-
Close, no Content-Length. No way to tell if the response is complete.
X-HOSTIP: 213.251.166.36
X-EGRESSPORT: 49501
X-CLIENTPORT: 49500

== TIMING INFO ============
ClientConnected: 23:26:13:9394
ClientDoneRequest: 23:26:13:9404
Gateway Determination: 0ms
DNS Lookup: 0ms
TCP/IP Connect: 125ms
ServerGotRequest: 23:26:14:1074
ServerBeginResponse: 23:26:14:8535
ServerDoneResponse: 00:00:00:0000
ClientBeginResponse: 00:00:00:0000
ClientDoneResponse: 00:00:00:0000


The response was streamed to the client as it was received.

== WININET CACHE INFO ============
This URL is not present in the WinINET cache. [Code: 2]
* Note: The above represents WinINET's ~current~ cache state, not the
state at the time of the request

[EricLaw]

This suggests that whatever server you're using isn't returning
properly formatted HTTP.

Instead of returning, e.g.

HTTP/1.1 200 OK

the server is instead returning something like:

CRLFCRLFCRLF200 OK

What is the URL that is being requested?

[EricLaw]

I took a look at this. The problem is that the data isn't actually in
HTTP format, so it's an illegal response and cannot be proxied.

Here's what the server sends:

ICY 200 OK\r\n
icy-notice1: <BR>This stream requires <a href="http://
www.winamp.com/">Winamp</a><BR>\r\n
icy-notice2: Firehose Ultravox/SHOUTcast Relay Server/Linux v2.6.0<BR>
\r\n
icy-name: Drone Zone: Atmospheric ambient space music. Serve Best
Chilled. Safe with most medications. [SomaFM]\r\n
icy-genre: Techno Ambient Space\r\n
icy-url: http://www.somafm.com\r\n
content-type: audio/mpeg\r\n
icy-pub: 1\r\n
icy-br: 128\r\n

On Nov 6, 2:35 pm, romor <dejan....@gmail.com> wrote:

[romor]

Hm... data is mp3 stream

If I understand you right, it's not possible to stream internet radios
through Fiddler?
As that URL was just example - it happens with any URL that I used for
playback.

If that is true, than I don't understand this, from the help when
explaining how and why to turn off default "buffering mode":
"Streaming mode is also useful in some other cases, particularly when
visiting Internet Radio sites that deliver a never-ending stream of
MP3 data. An audio stream, by definition, is never complete, so
Fiddler's attempt to buffer it completely will always fail."
(http://www.fiddlertool.com/Fiddler/Help/Streaming.asp)

Thanks for your reply.

[EricLaw]

Fiddler is a HTTP proxy. The MP3 streams you're pointed to run over
the ICY protocol, which is shoutcast's streaming format. ICY is VERY
close to HTTP, but not exactly the same thing. Frankly, I'm surprised
they decided to make it just slightly different than HTTP, as the
differences mean that the protocol likely doesn't work over all HTTP
proxies as it easily could.

If a site streams music over the HTTP protocol (e.g. Pandora.com)
Fiddler will work with it just fine.

[romor]

Thank you for the explanation.
I obviously didn't understood some basic things.

Regards