guyguy2003
January 26th, 2006, 10:57 PM
Hi Guys! A weird issue:
I have migrated a website from an old server to a new one. One of the applications there is an aspx application that work with a web service under the same website (in different virtual directories). When calling the web service, it needs to authenticate the user (Integrated Windows Authentication & Digest) but whenever I am using host header for the web site I have created (say port 80 and 'Intranet' as the host header name) it will not send my credinals and I will get Unauthorized (the webservice needs the user credinals) or it will pop up a window asking my for my credinals which are never authenticated.
I have created a website and a virtual directory on an existing website, with no host headers (used a different port number on the new website) and copied the web service and the pages that call it there. It works fine, with the same security. If I try to call the webservice on the host-header site (changing the webservice address in web.config) or call the webservice on the non-host-header sites from the host header application, it doesn't work.
So I am pretty sure its the host header that gives me crap
Btw, I am working within a domain so all users are authenticated by the domain server.
Can anyone advice if this is a known issue, or suggest a way to fix this?
Thanks
Guy
I have migrated a website from an old server to a new one. One of the applications there is an aspx application that work with a web service under the same website (in different virtual directories). When calling the web service, it needs to authenticate the user (Integrated Windows Authentication & Digest) but whenever I am using host header for the web site I have created (say port 80 and 'Intranet' as the host header name) it will not send my credinals and I will get Unauthorized (the webservice needs the user credinals) or it will pop up a window asking my for my credinals which are never authenticated.
I have created a website and a virtual directory on an existing website, with no host headers (used a different port number on the new website) and copied the web service and the pages that call it there. It works fine, with the same security. If I try to call the webservice on the host-header site (changing the webservice address in web.config) or call the webservice on the non-host-header sites from the host header application, it doesn't work.
So I am pretty sure its the host header that gives me crap
Btw, I am working within a domain so all users are authenticated by the domain server.
Can anyone advice if this is a known issue, or suggest a way to fix this?
Thanks
Guy