- 🇺🇸United States bluegeek9
Drupal 7 in End of Life and no longer supported. We encourage you to upgrade to a supported version of Drupal. For more information, see https://www.drupal.org/upgrade → .
Due to compliance and security issues my client has this following requirement.
1) Mask the internal servers true network identity from the public.
The direction we were initially working toward was the site is configured as prod.XYZ-example.com but publicly it is accessed as www.example.com through the use of a proxy and routing. We got close but ran into issues due to the fact that Drupal rewrites everything back to $base_path which exposed the public to internal network information (ie css paths: http://prod.XYZ-example.com/path-to-css ) which also broke the site display as the internal URL doesn't resolve publicly.
Im looking for a solution that supports a single installation but operates identically with 2 URLs. Domain Alias looks to maybe do the trick but is it overkill? Is this what I need or is there a simple solution that I'm overlooking?
Thanks for any assistance.
Closed: outdated
3.9
- Domain Alias
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Drupal 7 in End of Life and no longer supported. We encourage you to upgrade to a supported version of Drupal. For more information, see https://www.drupal.org/upgrade → .