This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 188264 - Build-in JRuby update fails behind firewall requiring proxy authentication
Summary: Build-in JRuby update fails behind firewall requiring proxy authentication
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Gems (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: issues@ruby
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2010-07-01 08:25 UTC by Josy
Modified: 2011-01-28 20:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Proxy settings (13.09 KB, image/png)
2010-07-01 08:26 UTC, Josy
Details
Error (26.10 KB, image/png)
2010-07-01 08:27 UTC, Josy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josy 2010-07-01 08:25:14 UTC
This works with previous release Netbeans 6.8 / build-in jruby 1.4. Thus it is a regression.

Checking for netbeans updates with Netbeans 6.9 works fine.
Downloading and installing netbeans plugins with Netbeans 6.9 works fine.
Reporting a netbeans error does not work (socket error), likely due to authentication problems too. (This is another error!)

Gem update via jruby commandline according the following shema works fine:

gem update -p http://username:password@proxyname:portnumber



Gem update via Netbeans GUI works fine 
when under Tools->Options->Manual Proxy Setting Proxy the following is intered:
-Http Proxy: http://username:password@proxyname
-Port:       portnumber
-Use the same proxy settings for all protocols: yes
-Proxy Requires Authenticiation: no

However in this case checking Netbeans updates and downloading Netbeans plugins fails, as these do not understand the above proxy format.

Conclusion:
In Netbeans 6.9 there seems to be a problem when providing proxy authentication setting from Netbeans to jruby gems.

Note:
Replace "username", "password", "proxyname", "portnumber" by the applicable values for your firewall.
Comment 1 Josy 2010-07-01 08:26:43 UTC
Created attachment 100535 [details]
Proxy settings
Comment 2 Josy 2010-07-01 08:27:31 UTC
Created attachment 100536 [details]
Error