G
Guest
I have a strange problem with a website and a web service.
They're both on the same server, running Windows server 2003. The website is
set up as the default website for the server.
I've got the same code running in several different environments, it just so
happens this is the production server we're having problems with. Not ideal,
typically.
What happens is this.
When code tries to access the web service, it gets a "302 redirect" response
from the IIS.
If you go to a browser on a machine that can see the production server and
just type in the address of the web service, rather than getting the web
service interface page you get redirected to the default website and thrown
to the error page. Which doesn't come up, because you're not logged in
As best I can tell from looking thru the database activity the web service
is firing up, and not obviously throwing an error, altho it may be subtly
throwing an error. In any event, it's not logging anything anywhere, which is
should do if it catches an error.
This thing is secured out the wazzoo - SSL, only specific IP addresses
allowed, the whole bit.
Any ideas?
I'm going to crosspost this in one of the other news groups just to make
sure I've got all my bases covered.
They're both on the same server, running Windows server 2003. The website is
set up as the default website for the server.
I've got the same code running in several different environments, it just so
happens this is the production server we're having problems with. Not ideal,
typically.
What happens is this.
When code tries to access the web service, it gets a "302 redirect" response
from the IIS.
If you go to a browser on a machine that can see the production server and
just type in the address of the web service, rather than getting the web
service interface page you get redirected to the default website and thrown
to the error page. Which doesn't come up, because you're not logged in
As best I can tell from looking thru the database activity the web service
is firing up, and not obviously throwing an error, altho it may be subtly
throwing an error. In any event, it's not logging anything anywhere, which is
should do if it catches an error.
This thing is secured out the wazzoo - SSL, only specific IP addresses
allowed, the whole bit.
Any ideas?
I'm going to crosspost this in one of the other news groups just to make
sure I've got all my bases covered.