« Previous Next »

• 08-04-2009, 5:58 PM

  emerbrito Joined on 11-26-2005, 5:19 PM New Jersey / USA Posts 7

  WMS - Reverse Proxy and log propagation - getting user IP Reply Contact Hi folks; I'm running WMS on Win 2008 Enterprise. What I'm trying to acomplish here is get the log from the reverse proxies to be propagated to the origin server. Here is a quote from the "Logging Model for Windows Media Services" document: "When a client sends a log to a cache/proxy server, the cache/proxy server writes this log to its own log file and also propagates this log to the upstream server; however, the cache/proxy server removes information in some fields before sending it to the upstream server (for example, s-cpu-util and s-totalclients to protect its own privacy)." And it actually works exactly like this, all information about the client is propagated (player version, duration and stuff like that), however it removes the client's IP from the "c-IP" field and add the reverse proxy IP. So, a question I made on another post when talking about WMS: Is it by design or is it a bug? The only reason it would propagate a client connection log, is because on the other end, somebody needs the "client information", so, why switch the IP? Before somebody ask, we need the client IP to work on geolocation. Now... Do we need to (go to all the trouble of) create a custom logging plugin just to implement that? Or... is it a bug and we can continue work on hour solution and wait for a fix? Hope somebody can help me with this one. Thanks in advance.

• 08-05-2009, 8:16 AM

  In reply to

  jeff@zina.com Joined on 09-26-2003, 10:43 AM Naples, FL, USA Posts 2,096	Re: WMS - Reverse Proxy and log propagation - getting user IP Reply Contact emerbrito: why switch the IP?   Because that's what a proxy server does.  Nothing to do with IIS here. Jeff Look for Wrox's new book Professional IIS 7 in your local bookstore, or order now at Amazon.com

• 08-05-2009, 2:25 PM

  In reply to

  emerbrito Joined on 11-26-2005, 5:19 PM New Jersey / USA Posts 7

  Re: WMS - Reverse Proxy and log propagation - getting user IP Reply Contact jeff@zina.com: Nothing to do with IIS here. Hi Jeff; First off all, thanks for your attention and for use your time to try to answer to my post. But I have to tell you this, I'm a little disapointed. I always expected more from an MVP. Nobody said it has to do with IIS, it's all about Windows Media Services, however, this post is on a "IIS - MEDIA" forum, where i believe is the right place to talk about WMS since the teams are now working together, and just look at the post bellow and you are going to see somebody else agrees with that: http://forums.iis.net/t/1148538.aspx jeff@zina.com: Because that's what a proxy server does.  Not exactly. Once again I'm assuming you got me wrong. As a reverse proxy it works very well (and i said that before - i believe). Here I'm talking about the way it propagates the log. Let's say for each activity it create 2 log lines on the origin server. One line is to identify the proxy/distribution server connection, this one has to have the proxy server IP. The only purpose of the second line, which is the client log information propagated to the origin server, is to allow the origin server to record data from the client who connected through the proxy server. Here the IP on "c-ip" should be the client's IP. Just because it's the client information being propagated. I didn't find a single place on the documentation talking about this and if it's like that by design, would be nice to "hear" from the WMS team the reasons they make it that way. Anyone who wants to increase the network trafic by enabling the log propagation option wants the "client information" on the other side. Hope this time i made myself clear.