[
https://issues.apache.org/jira/browse/AIRAVATA-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047725#comment-17047725
]
Marcus Christie commented on AIRAVATA-3027:
-------------------------------------------
I tried this on our dev server:
{noformat:title=default.conf}
# Setup default virtual host as a catchall to prevent resolving to the first
defined virtual host
# This will show the welcome page when requesting on the ip address or server
default hostname
<VirtualHost _default_:80>
DocumentRoot "/www/default"
</VirtualHost>
<VirtualHost _default_:443>
DocumentRoot "/www/default"
</VirtualHost>
{noformat}
For some reason, the {{_default_:443}} entry was preventing all of the other
SSL configurations. Not sure why.
> 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)
