Summary: | HTTP 404s generated badly in some cases | ||
---|---|---|---|
Product: | Koha | Reporter: | Galen Charlton <gmcharlt> |
Component: | Architecture, internals, and plumbing | Assignee: | Galen Charlton <gmcharlt> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | minor | ||
Priority: | P5 - low | CC: | dcook, fridolin.somers |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11612 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23329 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30261 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | |||
Bug Blocks: | 10581 |
Description
Galen Charlton
2014-01-17 15:59:05 UTC
Indeed. I think there should be HTML static pages for all HTTP error codes. They should be used in both apache configuration and in GCI output (maybe adding methods into C4::Output). With Bug 30261, we should be able to use C4::Output::output_error() for any staff interface or OPAC page. (In reply to Fridolin Somers from comment #1) > Indeed. > I think there should be HTML static pages for all HTTP error codes. > They should be used in both apache configuration and in GCI output (maybe > adding methods into C4::Output). I like the idea of static HTML pages. I think we've avoided them because we want to use the templating and such for a common look and feel, but I was just thinking... we could generate the static HTML pages during an app build step. I suppose that wouldn't work well for a git deployment though... |