[GH-ISSUE #252] Separating frontail from its components #161

New issue

Open

opened 2026-03-03 16:05:44 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 16:05:44 +03:00

Owner

Originally created by @pmulgaonkar on GitHub (Mar 28, 2023).
Original GitHub issue: https://github.com/mthenw/frontail/issues/252

I am trying to display frontail in an iframe with a nginx/django frontend in a way that the authentication of the user can be done before the log is displayed. Setting up frontail with nginx (as in your documentation) works fine. Redirect to the frontail from django also works. I have the web browser go to http:///django-api where the authentication happens, and a HTTP redirect to http:///frontail

My requirement is that a user directly entering http:///frontail should not work since it bypasses the django auth. To do that, I can set the /frontail location in the nginx config to be internal;

However, if I do that, when the browser requests the other components of frontail, namely /frontail/ansi_up.js, app.js, tinycon.min.js and socket.io.js they fail because /frontail is marked as internal.

Is there a way around this? Or a feature request to separate the url_paths for frontail from those of its assets. They could both point to the same backend via proxy_pass but the main entry point would be internal and the others external.

Originally created by @pmulgaonkar on GitHub (Mar 28, 2023). Original GitHub issue: https://github.com/mthenw/frontail/issues/252 I am trying to display frontail in an iframe with a nginx/django frontend in a way that the authentication of the user can be done before the log is displayed. Setting up frontail with nginx (as in your documentation) works fine. Redirect to the frontail from django also works. I have the web browser go to http://<ip>/django-api where the authentication happens, and a HTTP redirect to http://<ip>/frontail My requirement is that a user directly entering http://<ip>/frontail should not work since it bypasses the django auth. To do that, I can set the /frontail location in the nginx config to be internal; However, if I do that, when the browser requests the other components of frontail, namely /frontail/ansi_up.js, app.js, tinycon.min.js and socket.io.js they fail because /frontail is marked as internal. Is there a way around this? Or a feature request to separate the url_paths for frontail from those of its assets. They could both point to the same backend via proxy_pass but the main entry point would be internal and the others external.