We are trying to use IISCosign 3.* on one of our Server 2003 machines behind 
our reverse proxy, and I am having a problem Cosigning a directory from the 
correct URL.  What I mean is, the directory I would like to protect is 
_actually_ at this address:

   http://webserver.example.com/blah/blah/blah

but because of the reverse proxy, it is also available at

   http://www.example.com/blah/blah/blah

If you browse to webserver.example.com/.... the page *is* protected, but not if 
you browse to www.example.com/.... 

The relevant section of our cosign.config.dll is:

<Service>
  <Name>cosign-webserver.example.com</Name>
  <Website>webserver.example.com</Website>
  <RequireFactor>lan</RequireFactor>
  <FactorIgnoreSuffixOn>false</FactorIgnoreSuffixOn>
  <FactorSuffix>-junk</FactorSuffix>
  <Protected>/blah/blah/blah</Protected>
</Service>

and the service is defined on the weblogin server like this:

service cosign-webserver.example.com            
http://webserver.example.com/cosign/valid       2       webserver.example.com

Traffic intended for www is proxied to webserver via these two lines in the 
reverse proxy config:

ProxyPass / http://webserver.example.com/
ProxyPassReverse / http://webserver.example.com

Does anyone know why this would be happening?

----------------------------------
Paul Woolcock
[email protected]

------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to