Re: Embedded WMP with SSL source

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



OK I guess I'm lost. Any chance of posting the URL - I can test it in
all those combinations you've listed, to see what's common.

Just out of interest, if you ignore the embedded part of the equation,
and open the URL as written in the web page within the standalone
media player on Mac / Win, does it work then ?

Cheers - Neil

On Fri, 25 Nov 2005 09:02:06 -0800, "iansugar"
<iansugar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Update on this one: With the embedded player (WMP 10) in Firefox, I
>right-click the player and look at properties. The Location field shows
>.\https://..., i.e. it has been prefixed with dot and slash. Doing the same
>thing with IE, there is no dot and slash and it works. That could explain it,
>but where did the .\ come from I wonder? Doesn't happen when the URL is http.
>
>On the Mac, I can't find out if the problem is similar because the embedded
>player doesn't show any options. It just pops up a window saying "Cannot open
>the file. Verify that the path and filename are correct and try again.".
>Again, when the source is http, it works.
>
>Regards, Ian
>
>"iansugar" wrote:
>
>> Thanks for the prompt message.
>>
>> It was configured to use settings of the browser. I have now tried it with
>> "Do not use a proxy server" but no difference.
>>
>> Note that it works fine with the embedded WMP in IE 6, even with https, but
>> in Firefox and on the Mac it fails, where it did work with http.
>>
>> Anyone have any other ideas?
>>
>> "Neil Smith [MVP Digital Media]" wrote:
>>
>> > On Fri, 25 Nov 2005 06:49:02 -0800, "iansugar"
>> > <iansugar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>> >
>> > >For an intranet application, I'm streaming .wmv files and showing in embedded
>> > >media player. With some experimentation with the markup, I can get this to
>> > >work with IE 6 and Firefox on Windows (with WMP 10.0), plus Safari and IE 5
>> > >on Mac OSX (with WMP 9.0).
>> > >
>> > >When the application is in production everything must be over SSL, but when
>> > >I test this, the embedded player in Firefox on Windows, and in Safari or IE
>> > >on OSX, fails. The only difference is the url switched to https rather than
>> > >http.
>> > >
>> > >Anybody any ideas? Is it possible to do cross-browser embedded video over SSL?
>> >
>> > Do you have an http proxy that's blocking the https request URL ?
>> >
>> > On your standalone player, if you go to Tools -> Options -> Network,
>> > for the http option, does the Proxy column say "None" or something
>> > else ?
>> >
>> > If it *has* a value other than "None", then choose HTTP and click
>> > Configure - does it help to choose "Do not use a proxy server" or
>> > "Bypass proxy server for local addresses" (or maybe *specify* do not
>> > use proxy for https://yadda address) ?
>> >
>> > Cheers - Neil
>> >

.



Relevant Pages

  • Re: Embedded WMP with SSL source
    ... player on Mac and/or Firefox when the source URL is https? ... Doesn't happen when the URL is http. ... >>Regards, Ian ...
    (microsoft.public.windowsmedia.player)
  • Re: Complaints about Windows 2000 and Windows Media 9
    ... the player appears to read through the `entries` ... The stream is distributed as ... The player will attempt all the http stream locations first. ... What I'd do really is to set up the mms protocols first in the ASX ...
    (microsoft.public.windowsmedia.player.web)
  • Re: Cant connect to some streams with MP11
    ... their players also support rtsp or http. ... The player will automatically fall back to the second ref stream ... an available server. ...
    (microsoft.public.windowsmedia.player)
  • Re: Konsolenbasierter http-streaming Player?
    ... scheinbar nicht http stream abspielen muss ich Euch hier damit belaestigen. ... Wer weiss welcher Player unter Linux HTTP-Streams in der Konsole abspielen ... HTTP bereitgestellte Datei meinst, dnn geht das. ...
    (de.comp.os.unix.linux.misc)
  • Re: Firefox and XSLT (local stylesheet works, server-based stylesheet fails)
    ... >> IE deliberately violates a mandatory requirement of the HTTP RFC, ... >> relevance is the MIME content-type sent by the server. ... >> I presume that Firefox conforms to RFC2616 at least as well as does ... > either extension ...
    (comp.text.xml)