HTTP code 200 returned for invalid pages

[mueller-ma]

When connection to the openHAB server and try to access to notifications api (it's only on cloud, so this should produce an error), I get http code 200:

$ curl http://openhabian:8080/api/v1/settings/notifications -v
[...]
< HTTP/1.1 200 OK
< ETag: "1624816166000"
< Content-Type: text/html
< Content-Length: 1215
< Server: Jetty(9.4.40.v20210413)
[...]

This causes the Android app to recognize the server as cloud instance and tries to parse the response as json, but it's html. IMO the server should respond with 404 for not found subpages.

Browser for reference:

Android issue: openhab/openhab-android#2662

[wborn]

This is not an openhab-core issue but an openhab-webui Main UI issue.

It uses routes.js to determine what to show. It routes to not-found.vue when no route matches.

You can also test it by uninstalling the Main UI:

bundle:uninstall org.openhab.ui

Then you get a 404 not found for that URL. 😉
Perhaps @ghys can help with this.

[ghys]

This was indeed changed in #964 and that's an example of a "side effect" I was warning about.
We could make changes to restrict URL patterns that would be serving the main UI (whitelist or blacklist).

[wborn]

Can you transfer this issue to the webui repo @kaikreuzer?