Windows 7 - HTTP Error 400 (bad request)

Asked By ohRonald on 26-Mar-09 02:32 PM

When I try to connect to WME, all I get is an http 400 error.  I assume this
means my browser has found and is talking to WME but WME is unhappy about
something else.

I am running screen capture, and I saved a file and tried encoding that
(looped), but still the same 400 error.

I am running Windows XP sp3 but it is Media Center Edition 2004.
There are some other issues with this specific version of Media Center, such
as Media Player 11 will not work with it. Perhaps it's related, perhaps not.

I'm all ears!  Any guesses?  Any way to troubleshoot?


Neil Smith [MVP Digital Media] replied on 26-Mar-09 04:34 PM
On Thu, 26 Mar 2009 11:32:03 -0700, ohRonaldo

Your browser is not supposed to connect to WME, and WME doesn't "talk"
HTTP to browsers hence the error code (bad request). It is not a web
server and you're trying to treat it like one, which won't work.

Instead, open windows media player, press CTRL + U to bring up "Open
URL" dialog, then type in the address of the encoder PC, for example (your IP will vary, as may the port) and
press enter

Cheers - Neil
Digital Media MVP : 2004-2009
ohRonald replied on 26-Mar-09 05:46 PM
Well that makes a lot of sense Neil, thank you for your very quick response.
And it is working as you expected.  Great!

One question though .. I was under the (apparently/obviously mistaken)
impression that WME acted as a streaming webserver -- I guess I really
expected it to return a MIME type that my browser would understand and then
my browser would launch wmplayer as if I had clicked a hyperlink pointing to
a .wmv file.

Ultimately, I am wanting to offer up some very limited live broadcast over
the web.  I know this is kinda basic stuff to ask you, but this means I'll
just have to have a page with a player EMBEDded?  How will I get wmplayer to
launch in its own window, rather than just stuck as an object in that page.

THANK YOU VERY MUCH, clearly I had a wrong impression and was completely
stuck.  So close yet so close! :D



(PS I can't believe how easy you've made this stuff.  Thanks to all at MS)
ohRonald replied on 27-Mar-09 11:43 AM
Neil Smith [MVP Digital Media] replied on 28-Mar-09 02:41 PM
No. For (at least) 3 reasons :

(1) Browsers support http, https, ftp, and occasionally some other
protocols for rendering. Not mms.

(2) Most browsers will simply fail when presented with an
unknown/unsupported protocol. That is the correct behaviour.

In some cases IE *may* hand off a protocol to a registered handler,
which in *some* cases would be WMP (but it's not guaranteed and
therefore unreliable to try this)

(3) mms is depracated and already removed from WMP11 and 12, so you
would cause yourself a lot of forwards-pain by trying to use that
protocol. This document details the changes in WMP protocol support
between versions, you can see it's inconsistent :

Cheers - Neil

On Fri, 27 Mar 2009 08:43:02 -0700, ohRonaldo

Digital Media MVP : 2004-2009
Neil Smith [MVP Digital Media] replied on 28-Mar-09 07:16 PM
On Sat, 28 Mar 2009 12:55:03 -0700, ohRonaldo

Yes - the Player, not the Browser. They are entirely different
applications, and you cannot extrapolate from one to t'other.

Are you sill typing this into the browser address bar ?

My advice is not to, and use the player embedded in a web page, with a
fullscreen option. Otherwise you're leaving the end-user experience
open to only-working-on-your-dev-machine, leading to unhappy
customers, no invoices paid, and so forth.

Using HTTP *explicitly*, in some circumstances, yes. There's no
problem in actually enabling HTTP playback, as that may be the only
way to get your content past restrictive corporate or .edu firewalls

The best plan is to leave the player and the media server to correctly
negotiate the most effective delivery method available, rather than
second guessing the work of years of media streaming experts who made
protocol rollover possible.

You fluked it. Now install VideoLAN player - or another player (like
RealPlayer) which also knows how to handle these URLs, and see what
the experience is. Now multiply that by 100x for end users with a wide
variety of misconfigured / non-default systems.

They'll phone YOU (more likely your boss or your customer) when it
doesn't "work", and the only details you will have is "It doesn't
wotk", and you're hosed (and possibly looking for a new job)

Are you close to retirement ?
Cool, hope it works out ;-))

Cheers - Neil
Digital Media MVP : 2004-2009