We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

Web Service Request Using localhost in the URL gives 404 error

anyoneis
anyoneis asked
on
Medium Priority
670 Views
Last Modified: 2007-12-19
System:
     IIS 5.0 Windows 2000 Advanced Server.
     ASP.NET 1.1
     Multiple Layers of web services, all running on the same server.

I recently was making a minor change to a web service that had not been changed for about a year. I could not get the changes to work. I tried restoring the old source files and I still could not get it to work.

I eventually figured out that the URL I had been using for the last 3 years was causing the problem. Web service WSA called web service WSB using a dynamic URL: "http://localhost/WSB/WSB.asmx".

When I changed "localhost" to the name of the machine that both web services are on, it worked. When I changed "localhost" to "appserver", which is the string just below "localhost" in my System32\Drivers\Etc\hosts file, and which also resolves to 127.0.0.1, it also works.

When I use "localhost", I get a 404 error, and the error I get indicates that instead of looking in the directory which is defined for the application: C:\WebStuff\WSB, IIS is looking in C:\inetpub\wwwroot\WSB.

What is going on here? I am assuming that the application WSA, or at least the Web Service Proxy, had not been recompiled for over a year, and by refreshing the web service reference, I cause that recompile. But, the URL is not compiled in, it is specified at runtime.

Thanks,
David
Comment
Watch Question

Have yo uenabled virtual servers in IIS??
anyoneisSoftware Developer
Top Expert 2006

Author

Commented:
No. These web services are located on the default web site.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
anyoneisSoftware Developer
Top Expert 2006

Author

Commented:
Hmm. Well, now that you mention it... there is another web site defined called localhost. Perhaps what happened was that someone enabled it and caused my problem. If I understand virtual servers correctly, this site would get all messages referencing localhost, using the host header mechanism. But, how could it just pop up as a problem.

i am running off to ASPNET Connections for a week, so I'll look back into this in a week. Thanks for your ideas!

David

anyoneisSoftware Developer
Top Expert 2006

Author

Commented:
I haven't had time to test this, but I am fairly confident that manav_mathur's hypothesis is correct. So, let's close this!

Thank you!
David
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.