Project

Profile

Help

Issue #1486

closed

TemplateDoesNotExist exception for '404.html' raised on v3 API endpoint

Added by bmbouter about 8 years ago. Updated almost 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.7.1
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

I have not encountered this bug in practice, but I'm confident it exists because of the existence of issue #1485.

To reproduce do the following:

1. Make a url request to a url handled by the Django project handling requests to the /srv/pulp/puppet_forge.wsgi wsgi environment. This URL needs to be invalid such that you expect a 404 to be returned
2. Observe you'll see a TemplateDoesNotExist exception based on 404.html

To fix this we should do something similar to what we did in platform[0]. NOTE It's important to use *args and **kwargs on the handler implemented because newer version of Django change the handler signature in backwards incompatible ways. This was done here[1].

[0]: https://github.com/bmbouter/pulp/commit/996e4366742db143b366c6cccab7231ce0da4904
[1]: https://github.com/bmbouter/pulp/commit/996e4366742db143b366c6cccab7231ce0da4904#diff-0f102dc73ff02451924f2fdaa7df179eR117


Related issues

Related to Puppet Support - Issue #1485: TemplateDoesNotExist exception for '500.html' raised on v3 API endpointCLOSED - WONTFIXActions
Related to Pulp - Issue #1140: API call to URLs that do not exist cause 500s on RHEL 6CLOSED - CURRENTRELEASEbmbouterActions

Also available in: Atom PDF