The question is, how do I use the foreach construct in the nginx
configuration file?
> I am using openresty
> nginx -version
> nginx version: openresty/1.21.4.1
> This fails:
>
>
>
>> foreach $domain in $server_name {
>>>
>> ssl_certificate /etc/letsencrypt/live/$domain/fullchain.pem;
>>
I am using openresty
nginx -version
nginx version: openresty/1.21.4.1
> foreach $domain in $server_name {
>>
> ssl_certificate /etc/letsencrypt/live/$domain/fullchain.pem;
> ssl_certificate_key /etc/letsencrypt/live/$domain/privkey.pem;
> }
>
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
>
>
Hi Jonas,
> On 15 Feb 2023, at 21:50, Jonas Hünig via nginx-devel
> wrote:
>
> Hi,
>
> I installed the new prebuild nginx package with http/3 support. This works
> very well for one server block, but when I add the listen directives to a
> second server block I get this error on configtest:
On Sun, Feb 19, 2023 at 05:49:48PM -0800, Ivo Welch wrote:
Hi there,
> thank you, F. I created a completely new ubuntu VM, with a completely
> vanilla configuration and only this one extra location statement at
> http://164.67.176.22/ , describing the nginx configuration and
> referencing its /
