Hi Francis,
> I've read your description, and I confess I'm not sure what benefit
> auth_request within nginx gives you. It looks like your application is
> doing its own auth check on every request anyway, so having nginx do
> the same thing seems redundant. I'm probably missing something.
can u
Upgraded to 1.11
Now, things get worse, I am not being prompted for any credentials (even
with all browser cache cleared), even with the following
/etc/nginx/conf.d/default.conf
##
server {
listen 443 ssl;
s
Hello,
On 4/12/2017 12:59 PM, Maxim Dounin wrote:
It's just a matter of providing upstream servers
with a way to push resources, e.g., via something like the
X-Accel-Push header or something like this. This doesn't need
HTTP/2 between nginx and upstream servers.
On 4/12/2017 2:13 PM, Igal @ L
> Please watch the clip at https://youtu.be/QpLtBftqM04?t=34m51s until
> about 36m12s where Simone Bordet, a Jetty developer, claims that
> HA Proxy is a better proxy solution than nginx because it talks
> HTTP/2 to the Upstream.
This statement is misleading.
As of now, haproxy does not support H
On Wed, Apr 12, 2017 at 06:13:19PM +0530, Ajay Garg wrote:
Hi there,
> We are facing the following issue :
>
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the
> remote resource at https://1.2.3.4/. (Reason: CORS header 'Access-Control-
> Allow-Origin' missing).
What's
Hi,
How does nginx balances traffic to upstream with different weight? If I
have 3 servers in upstream, with weight 1, 2, 4, assuming all are healthy,
will nginx send traffic to server 1, 2, 3, 2, 3, 3, 3 or 1, 2, 2, 3, 3, 3,
3? If I have two servers with both weight 50, will nginx will 50 request
On Wed, Apr 12, 2017 at 05:50:56AM -0400, zaidahmd wrote:
Hi there,
> Below I will explain my application with NGINX configuration I have
> performed and the code snippets/references for future users.
I've read your description, and I confess I'm not sure what benefit
auth_request within nginx
Thank you, Maxim and Valentin, for your prompt replies. I will reply
here to both so that we can maintain a single thread for this issue:
On 4/12/2017 12:57 PM, Valentin V. Bartenev wrote:
Server Push doesn't require HTTP/2 from the Upstream side. Moreover,
upstream usually don't have access
Hello!
On Wed, Apr 12, 2017 at 11:40:16AM -0700, Igal @ Lucee.org wrote:
> According to https://www.nginx.com/blog/http2-module-nginx/#QandA nginx
> only supports HTTP/2 on the client side, but it is possible to configure
> proxy_pass to use HTTP/2.
>
> There is a huge benefit in supporting HT
On Wednesday 12 April 2017 11:40:16 Igal @ Lucee.org wrote:
> According to https://www.nginx.com/blog/http2-module-nginx/#QandA nginx
> only supports HTTP/2 on the client side, but it is possible to configure
> proxy_pass to use HTTP/2.
>
> There is a huge benefit in supporting HTTP/2 on the Ups
Hello everyone,
TL;DR: When proxying UDP packets through nginx, is there a way for nginx to
preserve its initial source port for subsequent packets? This is to be used
during a DTLS handshake.
Outlined version: This issue arose when proxying UDP packets, more
specifically establishing an DTLS con
According to https://www.nginx.com/blog/http2-module-nginx/#QandA nginx
only supports HTTP/2 on the client side, but it is possible to configure
proxy_pass to use HTTP/2.
There is a huge benefit in supporting HTTP/2 on the Upstream, as that
will allow the Upstream servers to perform HTTP/2 Pus
Vladimir Homutov Wrote:
---
> On Tue, Mar 28, 2017 at 12:25:35PM +0300, Vladimir Homutov wrote:
> > instead of normal DTLS.
>
> i meant SSL (TLS) of course.
> ___
> nginx mailing list
> nginx@nginx.org
Maxim,
On 4/12/2017 5:57 AM, Maxim Dounin wrote:
On Windows, nginx uses select() system call to handle connection
events. This syscall implies fixed-size bitmasks to pass file
descriptors from userland to kernel and back. Size of these
bitmasks can be only specified during compilation, and 10
Hi Richard.
Thanks for the help.
I added 'always' as the last argument in all the "add_header" and
"proxy_set_header" directives.
Unfortunately, I receive the following on the very first "add_header"
directive ::
#
2017/04/12 17:18:22 [emerg] 2
Hello Nginx users,
Now available: Nginx 1.12.0 for Windows
https://kevinworthington.com/nginxwin1120
(32-bit and 64-bit versions)
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.
Announce
Changes with nginx 1.12.012 Apr 2017
*) 1.12.x stable branch.
--
Maxim Dounin
http://nginx.org/
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Your are using auth_basic, so the 401 response code is not in the range
that add_header works with ("Adds the specified field to a response header
provided that the response code equals 200, 201, 204, 206, 301, 302, 303,
304, or 307."). You need to use "always" if you want to include the header
in
For the record, here is the server-block ::
#
server {
listen 443 ssl;
ssl_certificate /etc/nginx/ssl/nginx.crt;
ssl_certificate_key /etc/nginx/ssl/nginx.key;
add_header 'Acc
You can if you use the web portal at https://forum.nginx.org/
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,273547,273556#msg-273556
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Wed, Apr 12, 2017 at 07:40:25AM -0400, zaidahmd wrote:
> I need to edit one reply to a topic in this list and need to know how to
> perform it. I cannot see any edit or delete button.
>
> I have been using stackoverflow where edits and delete is allowed to the
> users.
This is a maili
Hello!
On Tue, Apr 11, 2017 at 09:37:46PM -0700, Igal @ Lucee.org wrote:
> Is there a technical reason for the 1,024 Connections Limit on Windows?
>
> http://nginx.org/en/docs/windows.html#known_issues
>
> Surely the OS can handle many more connections than that.
On Windows, nginx uses select(
Sorry for the idiotic question.
Just checked, multiple sockets are created on each side of the ssh-reverse
tunnel.
So, seems the 502-Bad-Gateway error is due to other (network-slowness)
issues.
Sorry again.
Thanks and Regards,
Ajay
On Wed, Apr 12, 2017 at 12:38 PM, Ajay Garg wrote:
> Hi All.
Hi All.
We are facing the following issue :
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the
remote resource at https://1.2.3.4/. (Reason: CORS header 'Access-Control-
Allow-Origin' missing).
Have tried everything I could find on the google, but nothing works
(whatever
Hi,
I need to edit one reply to a topic in this list and need to know how to
perform it. I cannot see any edit or delete button.
I have been using stackoverflow where edits and delete is allowed to the
users.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,273547,273547#msg-273547
__
Hi Francis,
Thanks for your interest. I would certainly like to contribute for the
future implementers of NGINX reverse proxy with API gateway functionality.
Below I will explain my application with NGINX configuration I have
performed and the code snippets/references for future users. If you like
Hi All.
Let's say, we have a server-block like
server {
listen 2001 ssl;
ssl_certificate /etc/nginx/ssl/nginx.crt;
ssl_certificate_key /etc/nginx/ssl/nginx.key;
27 matches
Mail list logo
