If someone have enabled this feature in his browser drupal logs all hit as 404. I'm not sure if this is more something that core need to handle, but it gives admins a wrong picture that users may typed in their browser. URLs like these don't require redirect.

I've seen a list on my url redirection list that looks like this:

content/how-to-
content/how-to-fo
content/how-to-foo
content/how-to-fooo
content/how-to-fooooo
content/how-to-foooooo
content/how-to-foooooo-
content/how-to-foooooo-ba
content/how-to-foooooo-bar
content/how-to-foooooo-bar-
content/how-to-foooooo-bar-f
content/how-to-foooooo-bar-fa
content/how-to-foooooo-bar-fac
content/how-to-foooooo-bar-factory
content/how-to-foooooo-bar-factory-
content/how-to-foooooo-bar-factory-s

hope you get it... we had the same discussion already in #1096478: Make Google Analytics stats more accurate by watching X-PURPOSE and X-MOZ headers, but for GA it's not really a problem as this are all HEAD requests that does not load the full page.

But it is a real problem for path_redirect...

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hass’s picture

Project: Path redirect » Drupal core
Issue summary: View changes

correction

hass’s picture

Project: Drupal core » Redirect
Version: 6.x-1.x-dev » 7.x-1.x-dev
Dave Reid’s picture

I'm a little unsure of what you mean? How is this related to redirects?

hass’s picture

The list is shown on the page with 404 that need a redirect... and this list becomes highly missleading.

Dave Reid’s picture

Status: Active » Closed (works as designed)

Ok. There's really not too much we can do here. We already sort the list of 404s by the number of times they have been encountered. Otherwise if you only have a bunch of 404s that have only been hit once, there's not a whole lot we can do to make this table better.

hass’s picture

Status: Closed (works as designed) » Active

Do you know how instant browsing works? It's for sure not only one hit if instant browsing becomes a default browser setting soon :-)

We can exclude all HEAD requests if the special X headers are send from a client. We should really do this!

Dave Reid’s picture

Status: Active » Closed (works as designed)

When Drupal core logs a 404 request, it does not store if the request is a HEAD or GET request. You would have to patch core to fix this, not redirect.

hass’s picture

Title: Instant browsing clutters URL redirection list dramatically » Instant browsing clutters 404 URL list dramatically
Project: Redirect » Drupal core
Version: 7.x-1.x-dev » 8.x-dev
Component: Code » base system
Status: Closed (works as designed) » Active

This was part of my question above. Moving to core.

pdrake’s picture

Because this can cause an inordinate amount of page not found watchdog entries that are not of significant value to the site owner, perhaps we should stop logging 404s in response to HEAD requests altogether.

pdrake’s picture

Priority: Major » Minor
Status: Active » Needs review

Bah, should have set this to needs review.

Status: Needs review » Needs work

The last submitted patch, drupal-stop_logging_HEAD_404s-1326396-8.patch, failed testing.

hass’s picture

Not all HEAD should be excluded. Only the ones with the instant browsing header. Linkchecker as an example check links with HEAD, too an we should see these if they are not instant

hass’s picture

Issue summary: View changes

a

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Issue summary: View changes
Status: Needs work » Postponed (maintainer needs more info)

Not sure I'm following but with D10 is this still a valid request? Only ask after 10 years of inactivity?

quietone’s picture

Issue tags: -instant browsing

Removing tag per the tag guidelines.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.