400 Bad Request While Using `django.test.client`

Question

I believe I am missing a fundamental setup.

I'm trying to test my API using Django's testing framework.

From the shell, I try:

from django.test import Client c = Client() r = c.get('/')

I get a 400 Bad Request, which is not the expected output.

Using a simple curl from the command line:

curl http://localhost

I get the expected output: {"detail":"Authentication credentials...

Am I missing something basic?

test.Client was returning an unexpected value, 400 Bad Request. It should have been returning json from my API. I wasn't sure what I had wrong in my setup. It looks like I just had the DEBUG flag set incorrectly (see my answer below). — Anthony C
– Anthony C, Commented Feb 15, 2015 at 21:32

insertjokehere · Accepted Answer · 2015-03-09 04:44:39Z

19

You can use the test client while DEBUG is False, you just need to add 'testserver' into your ALLOWED_HOSTS setting

answered Mar 9, 2015 at 4:44

insertjokehere

3971 silver badge10 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Dany Over a year ago

I kept getting the error in question even with DEBUG=True for some reason. Adding 'testserver' fixed it. If somebody could explain why is that so, I'd be grateful (tests were running fine with manage.py test, the problem persisted only in shell)

Anthony C · Accepted Answer · 2015-02-15 08:54:44Z

1

It looks like:

DEBUG = True

is needed in the settings.py file for this to work.

answered Feb 15, 2015 at 8:54

Anthony C

2,0003 gold badges23 silver badges40 bronze badges

1 Comment

Anthony C Over a year ago

I'll leave this answer unaccepted for a couple of days in case something better comes along.

Collectives™ on Stack Overflow

400 Bad Request While Using `django.test.client`

2 Answers 2

1 Comment

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Related