Changes between Initial Version and Version 1 of Ticket #27508, comment 3
- Timestamp:
- Nov 21, 2016, 6:43:53 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #27508, comment 3
initial v1 1 I only see the `path_info` in the debug view `technical_404_response()`, not the full path. Looking through the actual debug view confirms this behaviour as well -- the URL resolver is only passed the `path_info`, so if a `Resolver404` exception occurs, `exception.args[0]['path']` can only contain the `path_info`, not the `path`. The `e lse` clause uses `request.path_info`.1 I only see the `path_info` in the debug view `technical_404_response()`, not the full path. Looking through the actual debug view confirms this behaviour as well -- the URL resolver is only passed the `path_info`, so if a `Resolver404` exception occurs, `exception.args[0]['path']` can only contain the `path_info`, not the `path`. The `except` clause uses `request.path_info`.