HTTP 302 (Response.Redirect) to mms:// URL gives error, to http:// is ok.

Hello

Apologies for the cross-post, but I am not sure where the problem lies.

We have an ASP based website where we redirect users to MMS Publishing
Points.

So, guy clicks on http:// .asp link, we do a db update, then use
Response.Redirect to redirect them to a mms:// URL.

This works fine for me on W2K, XP Home and XP Pro with WMP 10, but I have
had many reports from visitors saying that they get connection errors and
access denied messages. I am sure they are using similar configurations to
me.

Now I am redirecting to http:// (so http streaming), and the problem seems
to have gone away. This is not ideal as we had intended to use RTSP to
stream our content.

Has anyone else experienced problems of this nature?

Thanks

David

 

Could be that the firewall is blocking all mms protocols, whereas http will
use the usual port 80.

 

Does it work any better if you redirect to an ASX file that contains a
reference to the mms URL ? You can just create the ASX on the fly on
your webserver, and send a video/x-ms-asf header.

I seem to remember there were occasions where the protocol switching
wasn't handled too well by the browser, i.e you'd send say a text/html
header by mistake (cause it's a web server) then the browser would end
up at a mms URL trying to ask it for the rest of the text/html
contents of course still using the http protocol.

Does it work better if you use a rtsp protocol anyway ?

The player since v9 has always rolled over to rtsp from mms anyway, so
it would save it having to negotiate that rollover.

HTH
Cheers - Neil