WMS Server Referring URL

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

javatopia - 19 Sep 2007 19:18 GMT

Hello,

I am writing an authorization plugin that needs to get the referring URL
from the client. So far, I've tried to get the log data out of the commant
context, and directly tried to query the WMS_USER_REFERER out of the user
context. Nothing works. I also enumerated the command, user, and presentation
contexts and found no field with the user's referring URL in it.

I am using WMS version 9.01.01.3841 and building my plugin using the
9.1.1.3841 DLL.

I've also tried binding the plugin on the server node as well as on a
publishing point, and neither produces the referring URL.

My test page is a simple HTML file with a link to an mms:// URL and an
embedded WMS player that directly plays an rtsp URL. Is there some other
magic trick to get the referring URL on the server??

Thanks

Signature

Jacob W Anderson
---
http://www.beyond-ordinary.com
http://www.extremeplannerlive.com
---
If you think it''''s expensive to hire a professional to do the job, wait
until you hire an amateur.

Reply to this Message

javatopia - 22 Sep 2007 21:58 GMT

I've tried getting the REFERER property from the user context and the
presentation context, on both the publishing point and the server. Yet,
nothing has worked. I've examined the contents of the user and presentation
contexts at both the server and publishing point, and yet no referer. I've
even enumerated the stream headers property out of the presentation context
and did not find the referer in there.

Neither MMS, RTSP, nor HTTP has produced this elusive property. Even in the
microsoft provided WMS logging plugin the referer is suspiciously missing
from the log entries.

I do not think Microsoft has implemented support for this header in the
current (9.1.1) version of WMS and not in the last WMS version.

Please correct me if I am wrong. Direct access to the WMS using MMS, RTSP,
or HTTP will not produce the referer URL.

Thanks

Signature

Jacob W Anderson
---
http://www.beyond-ordinary.com
http://www.extremeplannerlive.com
---
If you think it''''s expensive to hire a professional to do the job, wait
until you hire an amateur.

> Hello,
>
[quoted text clipped - 15 lines]
>
> Thanks

Reply to this Message

Vlad - 27 Sep 2007 04:01 GMT

It is possible to get the WMS_USER_REFERER from the user context. under
certain conditions. WMS_USER_REFERER is not YET available during the CONNECT
event, but available at later stages (OPEN, PLAY events)

Signature

Regards, Vladimir
http://voynex.com - custom software development, solutions for digital media
(pay per view, billing, protection, access control)

> Hello,
>
[quoted text clipped - 15 lines]
>
> Thanks

Reply to this Message

javatopia - 27 Sep 2007 15:38 GMT

Thanks for the response. Regreftully, though, I have to disagree. I set my
plugin to hit all authorize events, e.g. play, stop, describe, etc. None of
them produce the referer in any of the contexts (user, presentation, command).

I checked the WMS system log provided by the Microsoft logging plugin, and
it doesn't even contain the referring URL.

I am not using the WMS as an HTTP handler. My test cases are all with RTSP
protocol requests. Maybe you are able to get the referer through using the
HTTP protocol in the WMS? I did try that once, but did not see the referer
show up and did not see it even in the WMS log file.

Maybe there is some configuration property that I need to set in the WMS to
make it log the referer? Maybe some sort of extended logging option that is
specific to the WMS?

Signature

Jacob W Anderson
---
http://www.beyond-ordinary.com
http://www.extremeplannerlive.com
---
If you think it''''s expensive to hire a professional to do the job, wait
until you hire an amateur.

> It is possible to get the WMS_USER_REFERER from the user context. under
> certain conditions. WMS_USER_REFERER is not YET available during the CONNECT
[quoted text clipped - 19 lines]
> >
> > Thanks

Reply to this Message

Vlad - 02 Oct 2007 18:10 GMT

It may not contain the referring URL because you are playing the video from
the standalone player. An embedded player has to be used.

Signature

Regards, Vladimir
http://voynex.com - custom software development, solutions for digital media
(pay per view, billing, protection, access control)

> Thanks for the response. Regreftully, though, I have to disagree. I set my
> plugin to hit all authorize events, e.g. play, stop, describe, etc. None of
[quoted text clipped - 35 lines]
> > >
> > > Thanks

Reply to this Message

Pony Tsui - 11 Nov 2007 12:48 GMT

Try the WMS_EVENT_LOG at the IWMSEventNotificationPlugin, after
WMS_EVENT_LOG raised, You can get the WMS_USER_REFERER

Signature

Pony Tsui

> It may not contain the referring URL because you are playing the video from
> the standalone player. An embedded player has to be used.
[quoted text clipped - 38 lines]
> > > >
> > > > Thanks

Reply to this Message