Review main Abandoned

10281[FEATURE] Wrong HTTP headers when trying to access protected pages

Ingo Renner CR 0 V 0 Easy +18 −1 updated 12/14/14, 16:07

Commit message

When trying to access a login protected page while not being logged in
it may happen that a wrong header is sent.
The install tool allows to set a header for the page not found
handling: [FE][pageNotFound_handling_statheader]
The default value for this setting is "HTTP/1.0 404 Not Found"
In a case where access is denied because the user is not logged in,
this is the wrong header, it should be 403 instead. Therefore this patch
implements a new configuration [FE][pageForbidden_handling_statheader]

Review

  • Code review CR 0

    Imported before Forger kept the single votes, the next import adds them.

  • Verified V 0

    Imported before Forger kept the single votes, the next import adds them.

Issues 1

Files 2