401 HTTP request not handled

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Use a git repo with http auth
2. Put user and pass
3. Click next

What is the expected output? What do you see instead?

See the repo files, HTTP 401 challenge that is not properly handled. 

What version of the product are you using? On what operating system?

0.3.1  egit
3.4.1  eclipse
10.5.5 Mac OS X

Please provide any additional information below.

Original issue reported on code.google.com by cooldown@gmail.com on 10 Oct 2008 at 10:51

GoogleCodeExporter commented 8 years ago

I can confirm this with egit 0.4.0, eclipse 3.5 and kubuntu jaunty (32 & 64 bit)

Original comment by tymtheenchanter on 14 Jun 2009 at 2:10

GoogleCodeExporter commented 8 years ago

I can confirm this with egit 0.4.0, eclipse 3.5 and kubuntu jaunty (32 & 64 bit)

Original comment by tymtheenchanter on 14 Jun 2009 at 2:12

GoogleCodeExporter commented 8 years ago

I can confirm this on the following setups :
 -egit 0.5, eclipse 3.5 and windows xp
 -egit 0.5, eclipse 3.4 and Ubuntu 9.04

Original comment by xavier.t...@gmail.com on 8 Jul 2009 at 7:17

GoogleCodeExporter commented 8 years ago

Confirm as well: 
-egit 0.5.0, eclipse 3.4.2 on OSX 10.5.7

Basic webDAV authentication to access git repository; my git url looks like
http://git@hostname/project.git

Original comment by martha...@gmail.com on 15 Jul 2009 at 10:04

GoogleCodeExporter commented 8 years ago

I can confirm this with 0.5 and E3.4/3.5 on Ubuntu 9.04

Also ... this issue is 100% keeping me from using this plugin! Cant wait for a 
fix :)

Original comment by kiall%ma...@gtempaccount.com on 29 Jul 2009 at 7:05

GoogleCodeExporter commented 8 years ago

>Cant wait for a fix :)

Sure you can :)

Original comment by robin.ro...@gmail.com on 30 Jul 2009 at 2:12

GoogleCodeExporter commented 8 years ago

Same here on a Windows XP with Eclipse Galileo and egit 0.6.0.200911171911.
Is there any timeline when this bug will be fixed?

Original comment by hlibr...@gmail.com on 30 Nov 2009 at 1:00

GoogleCodeExporter commented 8 years ago

I know its *far* from ideal - but I got around this by adding some 
un-authenticated
apache aliases...

eg /git-kiall-<secret code here>/

There also limited to our LAN and my home ip (static ip @ home..) so that helps
somewhat....

Original comment by kiall%ma...@gtempaccount.com on 30 Nov 2009 at 1:04

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

Created entry in new bugs tracker

https://bugs.eclipse.org/bugs/show_bug.cgi?id=300785

let us see if this helps.

Original comment by rodrigo....@gmail.com on 26 Jan 2010 at 10:38

GoogleCodeExporter commented 8 years ago

Original comment by robin.ro...@gmail.com on 12 Jul 2010 at 5:26

Changed state: Duplicate

GoogleCodeExporter commented 8 years ago

Just for the record: What is the issue this one is a duplicate to? Cannot find 
any :(

Original comment by hlibr...@gmail.com on 12 Jul 2010 at 6:34

GoogleCodeExporter commented 8 years ago

See comment # 10. Looks like a duplicate to me. bugs.eclipse.org is the 
official tracker hence this bug is the duplicate even if the one at eclipse was 
enter after this one.

Sale! Everything must go! (to bugs.eclipse.org or /dev/null).

Original comment by robin.ro...@gmail.com on 13 Jul 2010 at 8:22

GoogleCodeExporter commented 8 years ago

Oh dear, sorry! Saw it too late that I am at the wrong issue tracker. I said 
nothing and meant it the complete other way around...

Original comment by hlibr...@gmail.com on 14 Jul 2010 at 6:25

denio7 / egit

401 HTTP request not handled #43