Django

Code

Ticket #718 (closed: wontfix)

Opened 3 years ago

Last modified 10 months ago

svn co behind stupid proxy

Reported by: vikrant@linmark.com Assigned to: jacob
Milestone: Component: Django Web site
Version: SVN Keywords: svn bad request error
Cc: Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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)

Attachments

Change History

11/02/05 20:26:27 changed by jacob

  • status changed from new to closed.
  • resolution set to worksforme.

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

11/02/05 21:03:55 changed by korpios@gmail.com

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

11/03/05 03:32:04 changed by jbennett@roanoke.edu

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.

11/03/05 08:25:37 changed by vikrant

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.

05/22/06 10:30:19 changed by phxx

  • status changed from closed to reopened.
  • priority changed from low to normal.
  • version changed from 1.0 to SVN.
  • milestone deleted.
  • keywords set to svn bad request error.
  • resolution deleted.
$ 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

05/22/06 10:37:47 changed by ubernostrum

  • status changed from reopened to closed.
  • resolution set to worksforme.

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.

05/22/06 16:46:38 changed 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.

12/17/07 08:30:32 changed by anonymous

  • status changed from closed to reopened.
  • resolution deleted.

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

12/17/07 12:43:14 changed by anonymous

  • component changed from Documentation to Django Web site.
  • summary changed from Installation problem using Subversion on Ubuntu version 5.10 to svn co behind stupid proxy.

12/17/07 12:53:09 changed by ubernostrum

  • status changed from reopened to closed.
  • resolution set to wontfix.

Don't reopen this.

12/18/07 06:12:26 changed by anonymous

  • status changed from closed to reopened.
  • resolution deleted.

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.

12/18/07 08:25:55 changed by ubernostrum

  • status changed from reopened to closed.
  • resolution set to wontfix.

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.

Add/Change #718 (svn co behind stupid proxy)




Change Properties
Action