Bug 13162 - WebProxy can not canged on second time
Summary: WebProxy can not canged on second time
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System (show other bugs)
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-07-10 18:10 UTC by Georg Kroeber
Modified: 2013-07-11 19:38 UTC (History)
2 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description Georg Kroeber 2013-07-10 18:10:05 UTC
If I use the following Code:

WebClient client = new WebClient ();
Uri proxyURI = new Uri("http://"+proxyurl + ":" + proxyport+"");
client.Proxy = new WebProxy(proxyURI);
string output = client.DownloadString (new System.Uri(checkurl));

everything is fine.

But if I change the Proxy and use client.DownloadString again the 
System uses the first and not the new defined Proxy.

On Windows Visual C# works it correct.
Comment 1 Georg Kroeber 2013-07-11 19:37:56 UTC
Now I have transfered the compiled .exe on a Debian Linux-Server.
It works correct on the Linux Server.

Version used on Debian
mono -V
Mono JIT compiler version 2.10.9 (tarball Fr 12. Jul 01:12:14 CEST 2013)
Copyright (C) 2002-2011 Novell, Inc, Xamarin, Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	LLVM:          supported, not enabled.
	GC:            Included Boehm (with typed GC and Parallel Mark)

Version used on OSX (default installed by Xamarin Studio)
Mono JIT compiler version 2.10.12 (mono-2-10/c9b270d Thu Mar  7 21:38:12 EST 2013)
Copyright (C) 2002-2012 Novell, Inc, Xamarin, Inc and Contributors. www.mono-project.com
	TLS:           normal
	SIGSEGV:       normal
	Notification:  kqueue
	Architecture:  x86
	Disabled:      none
	Misc:          softdebug 
	LLVM:          yes(2.9svn-mono)
	GC:            Included Boehm (with typed GC)

Note You need to log in before you can comment on or make changes to this bug.