Streaming azure

In the local development fabric streaming messages works. But in Azure I experience many the problems. The reply message was “the HTTP request includes a non-supported header” and the resultcode was 400 – bad request.
I noticed that a small test on port 85 did work in Azure. The difference in portnumber I noticed after a while and was totally unexpected. Looks like there is an ISA server on port 80 that doesn’t allows streaming. Port 85 looks clear of these kind of checks.
Below some screenshots of fiddler (must have) of the blocked port 80 and successfull port 85 session
Port 80 gets blocked by ISA
Port 85 works
Edit: after consulting a colleague I used my phone to connect to the service (tether) and discovered that works without a problem. The ISA server must be in my company network. Using wireshark for capturing the traffic confirmed my companies ISA tampered with the headers so no streaming over port 80 was possible. Sorry Microsoft, my bad. But what header can be so bad that streaming stops working ….
Test application and uploadservice sources can be downloaded from here so you can test your (companies) network too.

About erictummers

My work as a recruited developer changes almost every month. I like challenges and sharing the solutions with others. On my blog I’ll mostly post about my work, but expect an occasional home project, productivity tip and tooling review.
This entry was posted in Development and tagged , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s