Thanks.
I am considering the options.
On Mon, Feb 20, 2023 at 1:21 PM Payam Chychi wrote:
> +1 Francis
>
> Saint, I wonder if this might satisfy your ask indirectly.
>
> Assign a secondary ip address to a nic, and redirect to that ip for your
> iframe processing.
>
> Then you can apply a more sp
+1 Francis
Saint, I wonder if this might satisfy your ask indirectly.
Assign a secondary ip address to a nic, and redirect to that ip for your
iframe processing.
Then you can apply a more specific ACL at host or nginx level to control
iframe reachability, or even use a ip address thats only reac
On Sun, Feb 19, 2023 at 09:33:46AM -0500, Saint Michael wrote:
Hi there,
> it does not work:
> 404 Not Found
It appears that you are not asking "how do I ensure that a location{}
can only be used for internal redirects/requests".
> in the public location, /carrier_00163e1bb23c, I have
>
>
Thanks for your patience.
I publish a report, which takes 1 minute to complete.
So I send the users to a spinner, which has an Iframe inside.
While the spinner spins, the iframe runs the report from the /internal
location.
Once the report is ready, the spinner hides the div and replaces the
interna
You need to be more clear on what you are trying to do so we can help you.
Draw a diagram or something with the details.
You can use authentication and use that to protect and use at the same time
but again, you have left out some critical details as to what you are tying
to accomplish.
Nginx is
It uses the original IP of the user, not of the server.
That's why the ALLOW..DENY does not work either.
Nobody thought about this in Nginx.
On Sun, Feb 19, 2023 at 11:00 PM Payam Chychi wrote:
> Yes it does, but you are not providing enough on what you are doing, only
> what you want to do.
>
Yes it does, but you are not providing enough on what you are doing, only
what you want to do.
Run developer tools and see what your ip address is reported as.
On Sun, Feb 19, 2023 at 7:54 PM Saint Michael wrote:
> I also tried
>
> deny 192.168.1.1;
> allow 192.168.1.0/24;
> allow 10.1
I also tried
deny 192.168.1.1;
allow 192.168.1.0/24;
allow 10.1.1.0/16;
allow 2001:0db8::/32;
deny all;
and it does not work. It uses the remote IP of the caller.
So Nginx does not have a way to do this.
Thanks doe confirming it.
On Sun, Feb 19, 2023 at 10:32 PM Payam Chy
You need to learn two things:
1- learn to read the page and understand what the expected result should be
2- google!
Your problem has been well covered thousands of times before.
Your 404 is expected error code when you are accessing the website from
external.
Also, read
https://nginx.org/en/doc
Dear Francis
it does not work:
404 Not Found
this is my code
location /asr {
default_type 'text/html; charset=UTF-8';
internal;
}
location /carrier_00163e1bb23c {
default_type 'text/html; charset=UTF-8';
}
in the public location, /carrier_00163e1bb23c, I have
Your browse
On Sun, Feb 19, 2023 at 01:52:12AM -0500, Saint Michael wrote:
Hi there,
> it fails with forbidden. But I am using only from another location inside
> the same server.
>
> How do I protect internal service locations and at the same time use them?
If you are asking "how do I ensure that a locati
>
> I have two locations
/x
/yy
the public one is /y, nobody is supposed to access /x from the
Internet.
Inside /, I call /x, but if I do this:
location /asr {
default_type 'text/html; charset=UTF-8';
allow 127.0.0.1;
deny all;
it fails with forbidden. But I am usi
12 matches
Mail list logo
