Hi,
I compile a nginx for an 32bit system (ARM).
When I request a mp4 file which is larger than 2GB then it response with '416 Requested Range Not Satisfiable’.
The type of max_ranges is ngx_uint_t, I could not set it max than about 2000000000.
In this situation, I could I server the mp4 file correctly?
The ngx_size is set to 4 when I compile nginx.
So:
#ifndef NGX_MAX_SIZE_T_VALUE
#define NGX_MAX_SIZE_T_VALUE 2147483647
#endif
#ifndef NGX_SIZE_T_LEN
#define NGX_SIZE_T_LEN (sizeof("-2147483648") - 1)
#endif
#ifndef NGX_MAX_OFF_T_VALUE
#define NGX_MAX_OFF_T_VALUE 2147483647
#endif
#ifndef NGX_OFF_T_LEN
#define NGX_OFF_T_LEN (sizeof("-2147483648") - 1)
#endif
Config file:
location ~* .*\.(mp4|m3u8|m4s)$
{
max_ranges 2000000000;
include conf.d/options.conf;
add_header 'Access-Control-Allow-Origin' '*';
add_header 'Access-Control-Allow-Credentials' 'true';
root /mypath;
expires 6h;
}
The header of request:
Accept: */*
Accept-Encoding: identity;q=1, *;q=0
Accept-Language: zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7
Cache-Control: no-cache
Connection: keep-alive
Cookie: --------
Host: 192.168.199.245
Pragma: no-cache
Range: bytes=0-
Referer: -------------
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36 Edg/91.0.864.41
Hi All,
We’re trying to configure a client authentication on an Nginx 1.15.12 and
we noticed a “400 Bad Request - SSL Certificate Error” because a
certificate CA isn’t present into the certificates listed into
“ssl_client_certificate”. This is the configuration for the SSL
authentication.
ssl_verify_client optional;
ssl_client_certificate /usr/local/nginx/ca-test.pem;
Actually we would return a 401 error page instead a 400 error page but we
aren’t able to customize the HTTP code but only the message reported with
this configuration.
error_page 495 @error_ssl_495;
location @error_ssl_495{
return 401 'certificate invalid';
}
Is it possible to adjust also the http error code?
Thanks in advance,
Marcello
Hi,
On behalf of our marketing team I'd like to invite you, NGINX community
members, users and developers, to participate in the NGINX Annual
Community Survey.
There are 20 questions there. It will take around 10 minutes of your
valuable time to fill it:
The NGINX Annual Community Survey is open, and we would like to hear
from you. Over the past seven years, you've helped us improve our
solutions and evolve our product roadmap.
Please continue to share your experiences and ideas with us — we value
your feedback.
The anonymous survey is here:
https://survey.f5.com/v1/sites/nginx/SurveyResponse?at=1I0025DXE6KKG8JCV1KH…
Upon completion, you will receive an exclusive 90% discount code for the
NGINX swag store.
Thank you for helping shape the future of NGINX.
Regards,
NGINX team
--
Maxim Konovalov
_______________________________________________
nginx mailing list
nginx(a)nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
We have an responseHeader with technical information sent by the upstream
server tomcat.
We want to log this information in nginx and delete the header to avoid to
be visible in the response Header to the client.
log_format formatjson escape=json '{
'"tomcat_container_id": "$TOMCAT_CONTAINER_ID" }';
Nginx.conf in http {
map $sent_http_Container_Id $TOMCAT_CONTAINER_ID {
default $sent_http_Container_Id;
}
more_clear_headers 'Container-Id';
When I do this, my log tomcat_container_id is empty.
If I comment the more_clear_header command line, I have my log fill with the
right value but the header is also sent to the client.
So I don’t understand why my $TOMCAT_CONTAINER_ID Is clear when I delete the
header and not clear if I don’t.
Thanks for your help.
Posted at Nginx Forum: https://forum.nginx.org/read.php?2,293336,293336#msg-293336
_______________________________________________
nginx mailing list -- nginx(a)nginx.org
To unsubscribe send an email to nginx-leave(a)nginx.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Hello,
Is there a way to log individual websocket messages going through a nginx
server setup to proxy websocket as explained here
https://nginx.org/en/docs/http/websocket.html ?
-Chinmay
I had a wordpress blog and was working on Apache. I migrated the blog to
Nginx + php-fpm. But i have a problem with this.
My blog has RSS with example.com/feed URL , and i could see the feeds with
paged like this example -> http://www.kodcu.com/feed/?paged=45.
But in Nginx, this paged RSS urls dont work with my config. /feed and
/feed/?paged=X URLs shows top 10 content.
My nginx.conf same as below. How can i handle this problem?
user root root;
worker_processes 2;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 2;
types_hash_max_size 2048;
include /etc/nginx/mime.types;
default_type application/octet-stream;
error_log /var/log/nginx/error.log;
access_log off;
gzip on;
gzip_disable "msie6";
gzip_vary on;
gzip_proxied any;
gzip_comp_level 6;
gzip_buffers 16 8k;
gzip_http_version 1.1;
gzip_types text/html text/plain text/css application/json
application/x-javascript text/xml application/xml application/xml+rss
text/javascript;
##
# Virtual Host Configs
##
index index.php index.html index.htm;
## See here: http://wiki.nginx.org/WordPress
server {
server_name example.comwww.example.com;
root /var/www/example.com;
location = /favicon.ico {
log_not_found off;
access_log off;
}
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
location / {
# This is cool because no php is touched for static content
try_files $uri $uri/ /index.php?$args;
}
location ~ \.php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME
$document_root$fastcgi_script_name;
include fastcgi_params;
}
location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
expires max;
log_not_found off;
}
}
}
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,238692,238692#msg-238692
Dear,
I have a reverse-proxy in front of my two servers: web (apache2) and
email (nginx-iredmail).
The proxy-reverse is perfectly working with my web server running
Apache2, but I am not able to make it working for my email server.
The reverse-proxy and the email server are both running with the same
version of Nginx (1.9).
I have tried many configs without any success.
My last one:
***********************************************************************
server {
listen 446;
server_name email.domain.ltd;
location / {
proxy_pass https://email_server_ip:446;
proxy_ssl_certificate /etc/ssl/certs/cert.chained.crt;
proxy_ssl_certificate_key /etc/ssl/private/private.key;
proxy_ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
proxy_ssl_ciphers HIGH:!aNULL:!MD5;
proxy_ssl_trusted_certificate /etc/ssl/certs/cert.chained.crt;
proxy_ssl_verify on;
proxy_ssl_verify_depth 2;
proxy_ssl_session_reuse on;
error_log /var/log/nginx/error-proxy.log;
access_log /var/log/nginx/access-proxy.log;
}
}
Can I please have some help ??
Thx
--
Cordialement,
Thierry e-mail : lenaigst(a)maelenn.org
PGP Key: 0xB7E3B9CD
Hi Sergey,
I tried with clearing the connections header but NGINX is still sending the 5th response through a new source port. Let me give a more detailed configuration we have. Just to inform you, we have our own auth module instead of using the NGINX auth module. We call ngx_http_post_request to post subrequests and the code is almost the same as that of auth module. For the subrequest sent by auth module with the following configuration we expect NGINX to send requests through a new port for the first four connections and then reuse one of the ports for the fifth connection, especially when the requests are sequential.
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
sendfile on;
keepalive_timeout 65s;
include /etc/nginx/conf.d/*.conf;
proxy_socket_keepalive on;
server {
listen 9000;
server_name front-service;
ext_auth_fail_allow on;
error_log /var/log/nginx/error.log debug;
location / {
ext_auth_request /auth;
proxy_http_version 1.1;
proxy_set_header Connection "";
proxy_set_header Upgrade $http_upgrade;
proxy_set_header X-Real-Ip $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://localhost:8090;
location /auth {
internal;
proxy_set_header X-Req-Uri $request_uri;
proxy_set_header X-Method $request_method;
proxy_set_header X-Req-Host $host;
proxy_set_header X-Client-Addr $remote_addr:$remote_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_connect_timeout 5000ms;
proxy_read_timeout 5000ms;
proxy_http_version 1.1;
proxy_set_header Connection "";
proxy_pass http://ext-authz-upstream-server;
}
}
upstream ext-authz-upstream-server {
server 172.20.10.6:9006;
keepalive 4;
}
}
Could you please help on what we are missing?
Thanks,
Devashi
Date: Mon, 24 Jan 2022 17:56:33 +0300
From: "Sergey A. Osokin" <osa(a)freebsd.org.ru>
Subject: Re: Using single persistent socket to send subrequests
To: nginx(a)nginx.org
Message-ID: <Ye6+Ie0SM9YCKGby(a)FreeBSD.org.ru>
Content-Type: text/plain; charset=utf-8
Hi Devashi,
On Mon, Jan 24, 2022 at 05:52:56AM +0000, Devashi Tandon wrote:
>
> We have the following configuration:
>
> location / {
> proxy_http_version 1.1;
> proxy_pass http://ext-authz-upstream-server;
> }
>
> upstream ext-authz-upstream-server {
> server 172.20.10.6:9006;
> keepalive 4;
> }
>
> Do I need to add any other configuration to reuse the first four socket connections besides keepalive 4?
You'd need to review and slightly update the `location /' configuration
block by adding the following directive:
proxy_set_header Connection "";
Please visit the following link to get more details:
https://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive
--
Sergey Osokin