You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to alter the filename of the request and remember, that it is an error url. and then reprocess it.
I am afraid this will require some refactoring
I would suggest to use a new name scheme for error pages to allow displaying them in unauthorized mode and prevent calling them directly
like
error/404.* for a 404 error and the like.
What do you think?
The text was updated successfully, but these errors were encountered:
HHHartmann
added a commit
to HHHartmann/nodemcu-httpserver
that referenced
this issue
Apr 19, 2017
Customizable error pages seem like overkill for such a simple server but I'm not strongly opposed.
Storing them under "error/404.html" as you suggest sounds like the way to go to me.
The idea is to alter the filename of the request and remember, that it is an error url. and then reprocess it.
I am afraid this will require some refactoring
I would suggest to use a new name scheme for error pages to allow displaying them in unauthorized mode and prevent calling them directly
like
error/404.* for a 404 error and the like.
What do you think?
The text was updated successfully, but these errors were encountered: