Suppose you run Drupal on a machine using a domain name that is only defined in the hosts files of workstations that access the VM.

With that setup, Drupal will always have a bogus failure for "HTTP request status" in Administer > Reports > HTTP request status. It's bogus because HTTP requests actually work. Fixing it either requires the domain name served by some DNS server the Drupal server uses or adding the domain name to the server's hosts file.

I confirmed this locally by doing what's described at http://drupal.org/node/222454#comment-1229439.

This will affect people running a VM and using their hosts file to define a domain name. It could affect other use cases.

Comments

steinmb’s picture

steinmb commented
Version: 7.0-alpha1 » 7.x-dev
Issue summary: View changes

Consider this something that should be addressed in the server environment and not a Drupal core issue. Close?

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.