CODEWITHSUNDEEP
pythondjangohttpheroku
David Ingledow
David Ingledow

Reputation: 2095

I get an Error 400: Bad Request on custom Heroku domain, but works fine on foo.herokuapp.com

I've just pushed a Django project up to Heroku. It works fine at http://rtd-staging.herokuapp.com/rtd2015/, but for some reason I get a 400 error: Bad Request when I visit it using: http://staging.researchthroughdesign.org/rtd2015/

I know that the CNAME was setup correctly because during the process of pushing up to heroku it said that the Heroku app had crashed, so it was definitely pointing to the correct app.

Here is the log for the error:

2014-04-23T18:32:29.981976+00:00 heroku[router]: at=info method=GET path=/ host=staging.researchthroughdesign.org request_id=b8fe3ac9-e062-493b-b3bf-862c60e4001b fwd="82.34.146.252" dyno=web.1 connect=1ms service=7ms status=400 bytes=226

Upvotes: 29

Views: 18404

Answers (3)

Stéphane Bruckert
Stéphane Bruckert

Reputation: 22933

You have to set your website domain as an allowed host. Place this in your ./app/settings/settings.py:

ALLOWED_HOSTS = [".herokuapp.com", ".researchthroughdesign.org"]

In production you can even remove .herokuapp.com

Upvotes: 49

ZaMy
ZaMy

Reputation: 538

It was answered already but I just wanted to add if you are changing the app name on Heroku right after you change the git remote also make sure to do what was answered by @Leo because I was also struggling to why it was showing 400 response on the browser until I found this question.

Upvotes: 0

Léo Chaz Maltrait
Léo Chaz Maltrait

Reputation: 669

heroku config:set DJANGO_ALLOWED_HOSTS=.example.com,example.herokuapp.com

Upvotes: 9

Related Questions