Closed (duplicate)
Project:
Drupal core
Version:
6.13
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Jul 2009 at 20:55 UTC
Updated:
15 Oct 2012 at 15:16 UTC
When drupal_access_denied is called the function rewrites the actual path from the request and then sets it to the path of the access denied page setting, and after the rewrite there is no way to determine the path that was generated from the request. This is a problem if you wish to display a login form for the content of the access denied page. If you log the user in the form will redirect them to the path for the access_denied page, and not be able to redirect the user to the path they were at the beginning of the request.
Comments
Comment #1
gpk commentedI think you have tripped over #292565: Regression: Can't set /user to 403 page (was: login destination is broken), which is still waiting to be applied to 7.x.
Comment #2
naxoc commented#292565: Regression: Can't set /user to 403 page (was: login destination is broken) is in D7 and therefore also D8