Bug 1271 - Add-in manager doesn't work behind authenticated proxy on .NET
Summary: Add-in manager doesn't work behind authenticated proxy on .NET
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: PC Windows
: Low minor
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-10-05 15:22 UTC by Mike Christensen
Modified: 2012-05-02 11:10 UTC (History)
3 users (show)

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


Attachments
Error msg (118.56 KB, image/gif)
2011-10-05 15:22 UTC, Mike Christensen
Details
Config file to work-around the proxy issue (769 bytes, application/xml)
2011-10-05 18:20 UTC, Mike Christensen
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 1271 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Mike Christensen 2011-10-05 15:22:09 UTC
Created attachment 610 [details]
Error msg

Repro:

1) Get a job for a company that restricts the crap out of everything on their network.

2) Run MonoDevelop, Tools->Add-in Manager

3) Go to Gallery, click refresh icon

Results:

Exception thrown about proxy requiring logon info. (See attached screen cap)

Expected:

1) Better error message.

2) A place I can enter proxy logon information
or
3) It should just work, as both IE and Firefox seem to "detect" these settings off the network.
Comment 1 Mikayla Hutchinson [MSFT] 2011-10-05 17:55:43 UTC
Hmm, I can't reproduce step 1 ;-)

Anyway, on Windows, MD runs on .NET, and it should be using .NET's default proxy settings, which IIRC are loaded from IE.

You may be able to fix this by setting the default proxy to use default credentials. You can do it in MonoDevelop.exe.config, or you could fix it for *all* .NET apps in your system's machine.config. See http://stackoverflow.com/questions/914306 for some details.
Comment 2 Mike Christensen 2011-10-05 18:19:37 UTC
Yup!  This fixes the problem.  I'll attach a work-around .config file to the bug.

If you believe MonoDevelop should either somehow set this behavior at runtime, or ship with this .config file, then feel free to use this bug to track; if everything is behaving as expected, feel free to close.
Comment 3 Mike Christensen 2011-10-05 18:20:48 UTC
Created attachment 613 [details]
Config file to work-around the proxy issue

This will fix the issue:

	<system.net>
	  <defaultProxy enabled="true" useDefaultCredentials="true">
	    <proxy />
	    <bypasslist />
	  </defaultProxy>
	</system.net>
Comment 4 Mikayla Hutchinson [MSFT] 2011-10-05 19:03:03 UTC
I would argue this is a bug in the .NET default machine.config, but if we can work around it then we should.