Top | Newest First | Oldest First
It depends which webserver you're looking at, but I would search for "custom error pages" along with whichever browser you're using.
With apache, you'd used a directive like
ErrorDocument 500 /path/to/500.html
Of course, you have to be a server admin to do that since it would need permissions to change the config.
You could probably do it on .htaccess but you'd have to have certain things set on the server too.
But anyway, custom error pages is what you want to search out.
With apache, you'd used a directive like
ErrorDocument 500 /path/to/500.html
Of course, you have to be a server admin to do that since it would need permissions to change the config.
You could probably do it on .htaccess but you'd have to have certain things set on the server too.
But anyway, custom error pages is what you want to search out.
Northwest · M
@aboveaverageaveragejoe @LavenderTown
When you have no connection, you're not communicating with the server (no connection), so error processing is done locally.
The message you see from SW when there is no connection, is initiated by javascript code running on the local browser. Essentially they would do a window.addEventListener('online', () => somecode)
When you have no connection, you're not communicating with the server (no connection), so error processing is done locally.
The message you see from SW when there is no connection, is initiated by javascript code running on the local browser. Essentially they would do a window.addEventListener('online', () => somecode)