Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / August 2003

Tip: Looking for answers? Try searching our database.

Web service, web proxy and timeout problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
posthumecaver - 25 Aug 2003 16:17 GMT
Hello,

I have an very crazy problem.

I have 4 webservices I call from a rich client.

They are wroking perfectly in development environmen. They are also working
also perfectly when i call them from an Internet Web Server.

The problem, as always :)), at the customer.

Our customer has an squid Proxy server with authentication. I can not access
to the internet without setting Proxy settings and autheticating.

Well when I set the proxy property of the webservice and call it I always
get a timeout. In this stage I can say that I am doing something wrong but
the problem gets crazier with follwing input.

If I change the call to the web service to secure protocol (https)
everything is running perfect??????

So the proxy setting are true and working but I just getting timeouts for
http calls?????

Well then I said squid has a setting that is not letting http calls for Web
Service and to prove that I call from an Internet Explorer client the web
service. Guess what, it is running perfectly.

Can anybody help me with this puzzle.

Thx in advance.

MS

PS. I check the webserver logs, for http calls from richclients, none of
them reaching to the web service, but https calls are all there. From the
look of it either my calls are not leaving the client or the proxy server.
If it is not leaving the client I have an feeling it is some sort of a
thread deadlock in .NET Framework but why it is letting the https protocol
?????
posthumecaver - 26 Aug 2003 09:24 GMT
Never mind I found it.

That is a bug in WebProxy if u like to call a secure web service you have to
call

=new WebProxy("some.proxy.com",433)

not like
=new WebProxy("http://some.proxy.com",80)

or

=WebProxy.getDefaultProxy()

> Hello,
>
[quoted text clipped - 36 lines]
> thread deadlock in .NET Framework but why it is letting the https protocol
> ?????

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.