Hi, I am curious how is module type like NGX_HTTP_MODULE in
ngx_http_config.h is generated? Thanks!
#define NGX_HTTP_MODULE0x50545445 /* "HTTP" */
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,263474,263474#msg-263474
___
nginx mailing
> Can you name such applications that are only able to talk HTTP/2?
The developers I support would like to use GRPC [1] which is HTTP/2 only.
I need to provide an HA/LB system to support them.
I'm not saying this would be easy to implement, only that I need it :-)
Thank you for your help,
Nichol
I think what they are asking is to support the transport layer so that they
don't have to support both protocols on whatever endpoint they are
developing.
Maybe I'm wrong and someone has grand plans about multiplexing requests to
an upstream with http/2, but I haven't seen anyone ask for that expl
Wow, was struggling with that for a week already.
Can’t believe that was it.
Thank you Valentin and Francis!
> Op 15-dec.-2015, om 12:26 heeft Valentin V. Bartenev het
> volgende geschreven:
>
> On Tuesday 15 December 2015 11:56:43 Bram wrote:
>> Problem is that it will not accept anything be
On Tuesday 15 December 2015 11:56:43 Bram wrote:
> Problem is that it will not accept anything besides $remote_addr and
> $request_uri.
> For example:
>
> upstream loadbalancer {
> hash $server_name consistent:
There's a typo: you've used a colon at the end of the directive.
wbr,
On Tue, Dec 15, 2015 at 11:56:43AM +0100, Bram wrote:
Hi there,
> Problem is that it will not accept anything besides $remote_addr and
> $request_uri.
> For example:
>
> upstream loadbalancer {
> hash $server_name consistent:
Use ; not :
> #hash $request_uri consistent;
>
Problem is that it will not accept anything besides $remote_addr and
$request_uri.
For example:
upstream loadbalancer {
hash $server_name consistent:
#hash $request_uri consistent;
server 10.0.0.1:8080;
server 10.0.0.2:8080;
}
Will fail with:
invalid numb
On 12/15/15 12:53 PM, Valentin V. Bartenev wrote:
> On Tuesday 15 December 2015 09:44:45 Aleksey Portnov wrote:
>> Hello!
>>
>> Is it possible and correct something like:
>>
>> server {
>> listen 1.1.1.1:443 ssl;
>>
>> server_name sitename.de sitename.fr sitename.nl;
>>root /var/ww
On Tuesday 15 December 2015 10:13:35 Bram Verdonck wrote:
> Hi all,
>
>
> I wish to use load balancing in front of a shared webhosting cluster with
> multiple domains.
> To make optimal use of resources, it would make sense to do load balancing
> based on domain instead of random or based on IP
On Tuesday 15 December 2015 09:44:45 Aleksey Portnov wrote:
> Hello!
>
> Is it possible and correct something like:
>
> server {
> listen 1.1.1.1:443 ssl;
>
> server_name sitename.de sitename.fr sitename.nl;
>root /var/www/vhosts/Live/public_html;
>
>ssl_certificate /etc/ss
Hello!
Is it possible and correct something like:
server {
listen 1.1.1.1:443 ssl;
server_name sitename.de sitename.fr sitename.nl;
root /var/www/vhosts/Live/public_html;
ssl_certificate /etc/ssl/web/$host.pem;
ssl_certificate_key /etc/ssl/web/$host.key;
...
#commont
On Monday 14 December 2015 18:24:01 Nicholas Capo wrote:
> My specific use case is to support an HTTP/2 application behind a load
> balancer (reverse proxy).
>
> Also as a backend LB between services that could use a long running HTTP/2
> connection to do their communication.
>
> Places where I n
Thanks Maxim! You're right - we were looking in the wrong place - the
rewrite rule was just a red herring.
On Mon, Dec 14, 2015 at 5:25 PM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Dec 14, 2015 at 04:26:33PM -0800, Sunil Shah wrote:
>
> > We're running Jenkins behind an Nginx reverse proxy and s
Hi all,
I wish to use load balancing in front of a shared webhosting cluster with
multiple domains.
To make optimal use of resources, it would make sense to do load balancing
based on domain instead of random or based on IP.
I noticed that there is a hash parameter but I’m unable to use $server
14 matches
Mail list logo
