Opened 19 years ago
Closed 17 years ago
#718 closed defect (wontfix)
svn co behind stupid proxy
| Reported by: | Owned by: | Jacob | |
|---|---|---|---|
| Component: | *.djangoproject.com | Version: | dev |
| 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: | no | UI/UX: | no |
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 by , 19 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
comment:2 by , 19 years ago
Ditto (i.e., using Breezy here, works fine); furthermore, why is the initial poster using sudo for the checkout?
comment:3 by , 19 years ago
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 by , 19 years ago
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 by , 19 years ago
| Keywords: | svn bad request error added |
|---|---|
| milestone: | Version 1.0 |
| priority: | low → normal |
| Resolution: | worksforme |
| Status: | closed → reopened |
| Version: | 1.0 → SVN |
$ 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 by , 19 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | reopened → closed |
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 by , 19 years ago
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 by , 17 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
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 by , 17 years ago
| Component: | Documentation → Django Web site |
|---|---|
| Summary: | Installation problem using Subversion on Ubuntu version 5.10 → svn co behind stupid proxy |
comment:11 by , 17 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
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 by , 17 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | reopened → closed |
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.
I'm running Breezy too and it works just fine for me...