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 / .NET Framework / New Users / March 2006

Tip: Looking for answers? Try searching our database.

WebRequest & proxy problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Lloyd Dupont - 22 Mar 2006 07:44 GMT
In my auto-update code I donwload some files from the net with a WebRequest.
Some people having a proxy server reported problems.

IN a previous application I set the
WebRequest wr = ....;
wr.Proxy = WebProxy.GetDefaultProxy();

Which read proxy info from internet explorer. Great, exactly what I want.

But this method is now, in 2.0, apparemtly obsolete.
What could I use?

I read somewhere that someone suggested WebRequest.DefaultWebProxy, but
that's crazy, why set it if it's the default already?
I saw also the NetSectionGroup.DefaultProxy propery.

So now, what should I do?
Problem is I cannot test, we are not using proxy here .... :S and I don't
really know they work....
Joerg Jooss - 22 Mar 2006 19:56 GMT
Thus wrote Lloyd,

> In my auto-update code I donwload some files from the net with a
> WebRequest. Some people having a proxy server reported problems.
[quoted text clipped - 10 lines]
> but
> that's crazy, why set it if it's the default already?

Exactly. But don't forget that .NET 2.0 uses IE's proxy settings by default,
including the resolution of proxies via PACs. So there's actually nothing
to do...

> I saw also the NetSectionGroup.DefaultProxy propery.
> So now, what should I do?
> Problem is I cannot test, we are not using proxy here .... :S and I
> don't

That's a poor excuse for not testing.

"What, you run VS2005 on a Gateway PC? Sorry, we simply don't use Gateway
hardware, can you get one from a different vendor?"

:-O
Signature

Joerg Jooss
news-reply@joergjooss.d

Lloyd Dupont - 23 Mar 2006 01:45 GMT
> Exactly. But don't forget that .NET 2.0 uses IE's proxy settings by
> default, including the resolution of proxies via PACs. So there's actually
> nothing to do...

does it?
mmhh...
obviously these people are able to use internet explorer (as they downloaded
our product), but the WebRequest didn't work. So I wonder if it really
does....

>> I saw also the NetSectionGroup.DefaultProxy propery.
>> So now, what should I do?
[quoted text clipped - 4 lines]
> "What, you run VS2005 on a Gateway PC? Sorry, we simply don't use Gateway
> hardware, can you get one from a different vendor?"

Are you frustrated or something?
Of course I would like to test, but how could I?
I though here was a place of answer instead of useless taunt...... ?
Joerg Jooss - 23 Mar 2006 08:11 GMT
Thus wrote Lloyd,

>> Exactly. But don't forget that .NET 2.0 uses IE's proxy settings by
>> default, including the resolution of proxies via PACs. So there's
[quoted text clipped - 6 lines]
> our product), but the WebRequest didn't work. So I wonder if it really
> does....

It does for me (for a fixed proxy).

>>> I saw also the NetSectionGroup.DefaultProxy propery.
>>> So now, what should I do?
[quoted text clipped - 7 lines]
> Of course I would like to test, but how could I?
> I though here was a place of answer instead of useless taunt...... ?

I wasn't taunting, merely really wondering about software engineering practices
these days (assuming all of this happens in a business environment).

What about installing a simple proxy like Fiddler and test with that? It
can automatically register itself as system proxy, so you don't even have
to change your IE settings.
Signature

Joerg Jooss
news-reply@joergjooss.d

Lloyd Dupont - 24 Mar 2006 02:03 GMT
>>>> I saw also the NetSectionGroup.DefaultProxy propery.
>>>> So now, what should I do?
[quoted text clipped - 11 lines]
> practices these days (assuming all of this happens in a business
> environment).
hehehe...
what's wrong with business environment?
anyway I think the term to describe my company would be: an ISV, so it's
probably not what you call a 'business'.

> What about installing a simple proxy like Fiddler and test with that? It
> can automatically register itself as system proxy, so you don't even have
> to change your IE settings.
Fiddler you said?
Definitely a good tip, thanks!
Joerg Jooss - 24 Mar 2006 08:26 GMT
Thus wrote Lloyd,

>> I wasn't taunting, merely really wondering about software engineering
>> practices these days (assuming all of this happens in a business
[quoted text clipped - 5 lines]
> it's
> probably not what you call a 'business'.

I meant creating software as a business -- consulting, creating shrink wrapped
apps, etc. In that case I'd consider "we can't test, we have no proxy" a
bit... disappointing. If that software was some home grown app for friends
& familiy I wouldn't be that picky ;-)

>> What about installing a simple proxy like Fiddler and test with that?
>> It can automatically register itself as system proxy, so you don't
>> even have to change your IE settings.
>>
> Fiddler you said?
> Definitely a good tip, thanks!

This thing gets better with each release. Only yesterday I realized that
the latest version can create VSTS Web Tests from its captures, which is
awesome.

Cheers,
Signature

Joerg Jooss
news-reply@joergjooss.de


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.