The root domain URL “example.com” actually shows content for “Example Domain”. If “landing” parameter is modified in the url, user lands on the 404 page. OK…
However, but it would be very useful to have the same sort of behavior when any non-sensical directory is appended to the root domain in the main url. For example: example.com/xyz-garbage would ideally redirect to the 404 page. Instead, user just sees an ugly message on the root domain url:
{“code”:6007,“message”:“The specified resource was not found”,“errorData”:{}}
Unfortunately, we do not see a way to implement this. Because example.com/xyz-garbage is path to file. Example: URL to my app is https://myappbackendless.app. In the file system, it is located here:
If I try to follow a link like this: https://myappbackendless.app/settings.json, it shows me the setting (on screenshot) file’s content. The system cannot understand whether you want to receive file data or something else.
Hi Viktor: OK, makes sense. Probably not super important (since in theory it should hardly ever happen) but it would be nice to allow Backendless devs to style or otherwise prettify the view when someone goes to a bad place like https://domain.com/garbage… the message
“{“code”:6007,“message”:“The specified resource was not found”,“errorData”:{}}”
