rlkoshak
January 7, 2018, 6:43pm
4
Because that really isn’t how it works and fixing it just in the iOS app is not sufficient because any solution needs to work everywhere, Android, iOS, web broswers, etc and for ALL UIs including PaperUI, HABPanel, BasicUI, Habmin, etc…
To paraphrase Kai, “if this were easy it would have been fixed by now.”
opened 10:23AM - 03 Dec 15 UTC
enhancement
REST/SSE
migrated from Bugzilla [#423506](https://bugs.eclipse.org/bugs/show_bug.cgi?id=4… 23506)
status NEW severity _enhancement_ in component _Core_ for _---_
Reported in version _unspecified_ on platform _All_
Assigned to: Project Inbox
On 2013-12-07 15:55:42 -0500, Kai Kreuzer wrote:
> Migrated from https://code.google.com/p/openhab/issues/detail?id=235
https://code.google.com/archive/p/openhab/issues/235
opened 10:41PM - 17 May 17 UTC
As already mentioned in
https://community.openhab.org/t/using-nginx-reverse-p… roxy-authentication-and-https/
and
https://community.openhab.org/t/apache2-reverse-proxy-with-ldap-authentication-https-and-url-path-prefix/
it is often desired to run OH within the scope of an URL-path-prefix, i.e. *not* in the web-server's root (/).
It would be great, if the URL-path-prefix was configurable, but if this is very hard to achieve, at least a static, hard-coded path-prefix would be better than the current situation. Currently, OH runs in the web-server's root.
Rewriting many individual paths is very error-prone, likely never complete, and bloats the configuration. If there was at least a hard-coded path-prefix (e.g. "openhab/"), then one single SUBSTITUTE-rule would be sufficient to reliably remap everything.
People who want to use the root, e.g. to conveniently go to just https://host/ (instead of https://host/openhab/) could still do this easily by configuring redirects. These redirects would be necessary only for one or at most a hand full of entry-points. Thus, a single hard-coded path-prefix would IMHO be clearly preferable over the current situation.
I followed the tutorial here: http://docs.openhab.org/installation/security.html Everything worked as described: Nginx was doing the reverse proxy thing. But when I tried to replace “location / {” with “location /openhab {” and then access OH2 as https://my domain/openhab, all I am getting is that “openhab is not found”. I tried adding slashes at the end of openhab to no avail. I think the “not found” message is coming from Jetty, not Nginx.
Does anyone know how to rewrite the Nginx reverse pr…
openHAB is reverse-proxied from a non-root directory.
As far as I’ve been able to determine having set up reverse proxies for OH and other services this cannot be done without changes to OH itself and the changes described in the linked Issue would not solve the problem.
If you reverse proxy as the root directory it works just fine.
The problem is the reverse proxy cannot add the non-root directory to URLs generated by the JavaScript in the web pages it is serving up. To support that OH wo…
I see - thanks. It sounds like I can’t use a non-root location with Nginx server as well, for the same reason.
So the ideal solution would be for OH2 to have its own authentication. I heard some work is done in that direction - do you know if it close to be implemented?
