[jira] [Commented] (AIRAVATA-3027) Invalid HTTP_HOST header: 'django.simccs.scigap.org'. You may need to add 'django.simccs.scigap.org' to ALLOWED_HOSTS.

["Marcus Christie (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRAVATA-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052524#comment-17052524 ] 

Marcus Christie commented on AIRAVATA-3027:
-------------------------------------------

This is a good overview of the problem with trying to have a catch-all virtual host for SSL: https://serverfault.com/questions/843481/catch-all-https-vhost-on-apache-2-4

To make this work I'll need an SSL cert. I think just a self-signed certificate would be sufficient in this case.

> Invalid HTTP_HOST header: 'django.simccs.scigap.org'. You may need to add 'django.simccs.scigap.org' to ALLOWED_HOSTS.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-3027
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3027
>             Project: Airavata
>          Issue Type: Project
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> Getting lots of these error emails. I think the root cause is that HTTP requests on the portal server are matching some virtual host that isn't configured for that domain name. So for example, we might have a virtual host for django.example.com, another one for django.example2.org, etc. but then an HTTP request comes in for the servers IP address and Apache forwards the request to one of the Django servers. 
> Ultimately what I want is to configure a default virtual host in Apache that rejects a request for a non-matching domain name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)