Opened 11 years ago

Closed 9 years ago

#718 closed defect (wontfix)

svn co behind stupid proxy

Reported by: vikrant@… Owned by: Jacob
Component: *.djangoproject.com Version: master
Severity: normal Keywords: svn bad request error
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

When trying to checkout django via subversion on Ubuntu it throws a following errors:
$ sudo svn co http://code.djangoproject.com/svn/django/trunk/ django_src

svn: REPORT request failed on '/svn/!svn/bc/1056/django/trunk'
svn: REPORT of '/svn/!svn/bc/1056/django/trunk': 400 Bad Request (http://code.djangoproject.com)

Change History (12)

comment:1 Changed 11 years ago by Jacob

Resolution: worksforme
Status: newclosed

I'm running Breezy too and it works just fine for me...

comment:2 Changed 11 years ago by korpios@…

Ditto (i.e., using Breezy here, works fine); furthermore, why is the initial poster using sudo for the checkout?

comment:3 Changed 11 years ago by jbennett@…

Haven't had any problems with Breezy, didn't have any problems with Hoary.

And my guess for the reasoning behind 'sudo' is that this person is trying to checkout into a system directory that a normal user wouldn't have write access to.

comment:4 Changed 11 years ago by Vikrant Rathore

Yeah I am installing it in a directory where normal user do not have a write access so using sudo. I thought it would work but it didn't and thrown this error.

comment:5 Changed 11 years ago by Gregor Müllegger

Keywords: svn bad request error added
milestone: Version 1.0
priority: lownormal
Resolution: worksforme
Status: closedreopened
Version: 1.0SVN
$ svn co http://code.djangoproject.com/svn/django/trunk/
svn: REPORT Anfrage fehlgeschlagen auf '/svn/!svn/vcc/default'
svn: REPORT von '/svn/!svn/vcc/default': 400 Bad Request (http://code.djangoproject.com)

I've got nearly the same problem using [ArchLinux|www.archlinux.org] ...

Has noone any help?

thxx, phxx

comment:6 Changed 11 years ago by James Bennett

Resolution: worksforme
Status: reopenedclosed

Works for me on Ubuntu and various other platforms; this sounds more like a config problem on your end than something wrong with the repo.

comment:7 Changed 11 years ago by anonymous

this is probably related to a proxy. There are plenty of references if you google for "svn 400 bad request". If you can't circumvent the proxy, you have bad luck.

I'd advise to go to to your sysadmins.

comment:8 Changed 9 years ago by anonymous

Resolution: worksforme
Status: closedreopened

it is indeed a proxy problem. solution, however, is quite simple. it is to use encrypted connection (h ttps). I hope that it's not much of a trouble to enable it

comment:9 Changed 9 years ago by anonymous

Component: DocumentationDjango Web site
Summary: Installation problem using Subversion on Ubuntu version 5.10svn co behind stupid proxy

comment:10 Changed 9 years ago by James Bennett

Resolution: wontfix
Status: reopenedclosed

Don't reopen this.

comment:11 Changed 9 years ago by anonymous

Resolution: wontfix
Status: closedreopened

solution is simple.
it is explained.
don't reopen this is not an explanation.
if you're incapable of having server listening at 443 port write so.
thanks.

comment:12 Changed 9 years ago by James Bennett

Resolution: wontfix
Status: reopenedclosed

It is not the job of the Django project to perpetuate bad IT policies by helping people to work around them; therefore the repository will not be moved/reconfigured in a way which works around bad IT policies that prevent access to it. Therefore the status of this ticket is WONTFIX.

Do not reopen this ticket.

Note: See TracTickets for help on using tickets.
Back to Top