You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My reasoning is that I'm on a shitty At&t router & the damn thing doesn't resolve my local server at my hostname from my internal network. Which means that when I'm at home the hostname would be 192.168.1.* but when I'm out it's my domain. I'm okay with this behavior, but when I wanna make my own embedded apps for my local server I can't because it won't resolve when I'm outside the network. I would like it so that this would grab the hostname from the request info & embed it that way.
The text was updated successfully, but these errors were encountered:
Probably related to and solves the same problem as #120 which I am running into.
Same as above, my internal router (1) doesnt have DNS entries for local machines and (2) will resolve my FQDN to the external IP. The effect is that if I have another app on the same server (eg /transmission, or /jellyfin) and I access from a local IP (eg 192.168.1.x), the iframe loads from the internet whereas nextcloud loads from the local network. This is not ideal as the local network will likely be considerably faster than my router internet and may have relaxed security controls.
In the above issue the request was to allow relative URLs, which was rejected due to compat issues, but this is really the same kind of issue - compatibility / convenience for other apps sharing the same URL scheme. Just to add then, this proposal will need template variables for both the current hostname and protocol to ensure compatbility, so you can put in:
{proto}://{hostname}/something
Or alternatively, revisit the above issue and have logic that will automatically parse
/foo
as an implicit
{proto}://{hostname}/something
which should resolve to the proto / hostname of the current session, possibly falling back to the canonical if indeterminate
Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.
We hope that the reviewing process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, we would appreciate your feedback on your experience with our community management team.
Steps to reproduce
Expected behaviour
Expect to see http://localhost when clicked
Actual behaviour
I'm not allowed to save it with that.
My reasoning is that I'm on a shitty At&t router & the damn thing doesn't resolve my local server at my hostname from my internal network. Which means that when I'm at home the hostname would be 192.168.1.* but when I'm out it's my domain. I'm okay with this behavior, but when I wanna make my own embedded apps for my local server I can't because it won't resolve when I'm outside the network. I would like it so that this would grab the hostname from the request info & embed it that way.
The text was updated successfully, but these errors were encountered: