Quantcast
Channel: Nginx Forum - Nginx Mailing List - English
Viewing all 7229 articles
Browse latest View live

Typo in documentation... (1 reply)

$
0
0
Wasn't sure how to contact the webmaster as there is only a sales
contact form on the nginx website.... Would it kill them to have a
basic feedback form or email address?

I believe there's a typo on the following page:

https://docs.nginx.com/nginx/admin-guide/security-controls/controlling-access-proxied-http/

Specifically, under "Limiting the Bandwidth", last box there is the following:

location /download/ {
limit_conn addr 1;
limit_rate 1m;
limit_rate 50k;
}

I believe the first "limit_rate" is actually supposed to be
"limit_rate_after"...
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

ngx_http_catch_body_filter doesn't appear to work (no replies)

$
0
0
I'm trying to use the ngx_http_catch_body_filter example to capture request bodies from post (etc.) requests.

I started with the example here in the hg repo: https://www.nginx.com/resources/wiki/extending/examples/body_filter/

I changed the config to make it a dynamic nginx module.

I can see the `ngx_http_catch_body_init()` method getting called in the logs (I put an error log in that method).

When I try a proxied POST or file upload, `ngx_http_catch_body_filter()` never gets called.

Here's my modified source code and config. What am I doing wrong?

---- nginx.conf ----
...
load_module modules/ngx_http_catch_body_filter_module.so;
...
location /app1/ {
catch_body on;
proxy_pass http://localhost:8180/java_test_app/;

}

---- config ----
# (C) Maxim Dounin
# Configuration for ngx_http_catch_body_filter_module.

ngx_addon_name="ngx_http_catch_body_filter_module"

#HTTP_MODULES="$HTTP_MODULES \
# ngx_http_catch_body_filter_module"

NGX_ADDON_SRCS="$NGX_ADDON_SRCS \
$ngx_addon_dir/ngx_http_catch_body_filter_module.c"

ngx_module_type=HTTP_AUX_FILTER
ngx_module_srcs=$NGX_ADDON_SRCS
ngx_module_name=$ngx_addon_name

. auto/module

---- ngx_http_catch_body_filter_module.c ----

/*
* Copyright (C) Maxim Dounin
*/

#include <ngx_config.h>
#include <ngx_core.h>
#include <ngx_http.h>
#include <stddef.h>

typedef struct {
ngx_flag_t enable;
} ngx_http_catch_body_conf_t;


static void *ngx_http_catch_body_create_conf(ngx_conf_t *cf);

static char *ngx_http_catch_body_merge_conf(ngx_conf_t *cf, void *parent,
void *child);

static ngx_int_t ngx_http_catch_body_init(ngx_conf_t *cf);


static ngx_command_t ngx_http_catch_body_commands[] = {

{ngx_string("catch_body"),
NGX_HTTP_MAIN_CONF | NGX_HTTP_SRV_CONF | NGX_HTTP_LOC_CONF | NGX_CONF_FLAG,
ngx_conf_set_flag_slot,
NGX_HTTP_LOC_CONF_OFFSET,
offsetof(ngx_http_catch_body_conf_t, enable),
NULL},

ngx_null_command
};


static ngx_http_module_t ngx_http_catch_body_module_ctx = {
NULL, /* preconfiguration */
ngx_http_catch_body_init, /* postconfiguration */

NULL, /* create main configuration */
NULL, /* init main configuration */

NULL, /* create server configuration */
NULL, /* merge server configuration */

ngx_http_catch_body_create_conf, /* create location configuration */
ngx_http_catch_body_merge_conf /* merge location configuration */
};


ngx_module_t ngx_http_catch_body_filter_module = {
NGX_MODULE_V1,
&ngx_http_catch_body_module_ctx, /* module context */
ngx_http_catch_body_commands, /* module directives */
NGX_HTTP_MODULE, /* module type */
NULL, /* init master */
NULL, /* init module */
NULL, /* init process */
NULL, /* init thread */
NULL, /* exit thread */
NULL, /* exit process */
NULL, /* exit master */
NGX_MODULE_V1_PADDING
};


static ngx_http_request_body_filter_pt ngx_http_next_request_body_filter;


static ngx_int_t
ngx_http_catch_body_filter(ngx_http_request_t *r, ngx_chain_t *in) {
ngx_log_error(NGX_LOG_NOTICE, r->connection->log, 0, "catch request body filter");
fprintf(stderr, "catch request body filter\n");
return ngx_http_next_request_body_filter(r, in);
}


static void *
ngx_http_catch_body_create_conf(ngx_conf_t *cf) {
ngx_http_catch_body_conf_t *conf;

conf = ngx_pcalloc(cf->pool, sizeof(ngx_http_catch_body_conf_t));
if (conf == NULL) {
return NULL;
}

conf->enable = NGX_CONF_UNSET;
return conf;
}


static char *
ngx_http_catch_body_merge_conf(ngx_conf_t *cf, void *parent, void *child) {
ngx_http_catch_body_conf_t *prev = parent;
ngx_http_catch_body_conf_t *conf = child;

ngx_conf_merge_value(conf->enable, prev->enable, 0);
return NGX_CONF_OK;
}


static ngx_int_t
ngx_http_catch_body_init(ngx_conf_t *cf) {
ngx_log_error(NGX_LOG_NOTICE, cf->log, 0, "init catch request body filter");
ngx_http_next_request_body_filter = ngx_http_top_request_body_filter;
ngx_http_top_request_body_filter = ngx_http_catch_body_filter;
return NGX_OK;
}

Static content and Front Controller pattern under same base URI (no replies)

$
0
0
Hello, nginxers!

What's the best way to server static content as well as dynamic content
that uses the Front Controller pattern under the same base URI?

I'm dealing with a web app partially written in PHP that expects to
serve static content as well as dynamic PHP content, using the Front
Controller pattern, both under the same base URI. It expects to serve
static content if the file or directory exists. But if the file or
directory does not exist, it expects request rewriting according to the
Front Controller pattern like this:

----
Request Rewritten Request

/foo/ /foo/index.php
/foo/bar /foo/index.php/bar
/foo/bar/baz /foo/index.php/bar/baz
----

The following config works correctly:

----
location = /foo { return 301 $uri/$is_args$args; }

location /foo/ {
alias /srv/www/localhost/app/foo/1.0.0/;
index index.php;
try_files $uri $uri/ @foo_front_controller;
}

location ~ ^/foo/.*?[^/]\.php(?:/|$) {
error_page 418 = @foo_front_controller;
return 418;
}

location @foo_front_controller {
rewrite ^/foo(?!/index\.php)(/.+)$ /foo/index.php$1 last;
root /srv/www/localhost/app/foo/1.0.0;
fastcgi_split_path_info ^/foo(/.+?\.php)(/.*)?$;
include php-fpm.conf;
fastcgi_param REQUEST_URI $fastcgi_script_name$fastcgi_path_info$is_args$args;
}
----

I'm not a big fan of the location that sets the 418 error_page to the
@foo_front_controller named location, but I don't know of any other way
to essentially do a "return @foo_front_controller". Is there a better
way?

The whole point of the @foo_front_controller named location is so that
I can have one block that defines the Front Controller logic, and then
use it in both the "/foo/" location block in the try_files directive as
the fallback for when the file or directory does not exist and in the
location block right below it for requests that are for .php files.

Is this a good approach, or is there a better way?

Example content and requests are shown below.

Thank you!

Lewis

----
$ ls -al /srv/www/localhost/app/foo/1.0.0
total 8
drwxr-xr-x 2 root root 38 Oct 17 17:04 .
drwxr-xr-x 3 root root 19 Oct 17 16:37 ..
-rw-r--r-- 1 root root 209 Oct 17 17:04 index.php
-rw-r--r-- 1 root root 21 Oct 17 16:44 msg.txt
$ cat /srv/www/localhost/app/foo/1.0.0/index.php
<!doctype html>
<html lang=en>
<head>
<title>hello, world</title>
</head>
<body>
<?php echo '<p>hello, world</p>' . "\n"; ?>
<?php echo '<p>REQUEST_URI: ' . $_SERVER['REQUEST_URI'] . '</p>' . "\n"; ?>
</body>
</html>
$ cat /srv/www/localhost/app/foo/1.0.0/msg.txt
Use the Force, Luke.
$ curl http://localhost/foo/
<!doctype html>
<html lang=en>
<head>
<title>hello, world</title>
</head>
<body>
<p>hello, world</p>
<p>REQUEST_URI: /index.php</p>
</body>
</html>
$ curl http://localhost/foo/index.php
<!doctype html>
<html lang=en>
<head>
<title>hello, world</title>
</head>
<body>
<p>hello, world</p>
<p>REQUEST_URI: /index.php</p>
</body>
</html>
$ curl http://localhost/foo/bar
<!doctype html>
<html lang=en>
<head>
<title>hello, world</title>
</head>
<body>
<p>hello, world</p>
<p>REQUEST_URI: /index.php/bar</p>
</body>
</html>
$ curl http://localhost/foo/bar/baz
<!doctype html>
<html lang=en>
<head>
<title>hello, world</title>
</head>
<body>
<p>hello, world</p>
<p>REQUEST_URI: /index.php/bar/baz</p>
</body>
</html>
$ curl http://localhost/foo/msg.txt
Use the Force, Luke.
$ curl http://localhost/foo/msg-quux.txt
<!doctype html>
<html lang=en>
<head>
<title>hello, world</title>
</head>
<body>
<p>hello, world</p>
<p>REQUEST_URI: /index.php/msg-quux.txt</p>
</body>
</html>
----
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Revisiting the long-overdue "TODO always gunzip" in ngx_http_gunzip_filter_module.c (no replies)

$
0
0
Recently I was looking into having my upstream server gzip content
that is sent to nginx (which is acting as a reverse proxy) to reduce
local bandwidth. However, I needed to decompress the response so nginx
could do some manipulation, then obviously it would get re-compressed
(typically with brotli) before sending out to the client.

After finding numerous posts saying that "that feature doesn't exist",
then looking at the source of the gunzip module and finding the "TODO"
saying the exact thing I was looking for, I managed to find this old
post from 2013 where someone made a patch to do the exact thing
needed:

http://mailman.nginx.org/pipermail/nginx-devel/2013-January/003276.html

It's only about 11 lines of code, attached is a newer patch I did
against 1.17.4 since the gunzip source changed a bit. Basically the
patch adds the option "gunzip_force on;"

I do agree with the TODO comment in the source that having a way for
other modules to request decompression would be great, but also having
a configuration option (like this patch) is also a good feature.

After implementing this patch, and configuring the upstream server to
use gzip level 1 (figured maximize speed and minimize cpu usage), my
local bandwidth usage between the two immediately dropped 80-85%, and
I swear even the load levels dropped a hair, probably due to less
networking overhead, despite the compressing & decompressing of
content.

I realize there is probably a mile-long TODO list for nginx features,
but something so trivial like this patch has such a huge impact on
network usage and I'm sure a better implementation would still only be
a minimal code change. Just trying to give this a nudge so it's not
forgotten, as I did come across quite a few posts online into how to
do such a thing, so the demand is out there.

Jason
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

nginx-1.17.5 (no replies)

$
0
0
Changes with nginx 1.17.5 22 Oct 2019

*) Feature: now nginx uses ioctl(FIONREAD), if available, to avoid
reading from a fast connection for a long time.

*) Bugfix: incomplete escaped characters at the end of the request URI
were ignored.

*) Bugfix: "/." and "/.." at the end of the request URI were not
normalized.

*) Bugfix: in the "merge_slashes" directive.

*) Bugfix: in the "ignore_invalid_headers" directive.
Thanks to Alan Kemp.

*) Bugfix: nginx could not be built with MinGW-w64 gcc 8.1 or newer.


--
Maxim Dounin
http://nginx.org/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

njs-0.3.6 (no replies)

$
0
0
Hello,

I'm glad to announce a new release of NGINX JavaScript module (njs).

This release proceeds to extend the coverage of ECMAScript
specifications.

Notable new features:

- Function constructor:
: > var sum = new Function('a, b', 'return a + b');
: undefined
: > sum(2, 3)
: 5

You can learn more about njs:

- Overview and introduction: http://nginx.org/en/docs/njs/
- Presentation: https://youtu.be/Jc_L6UffFOs

Feel free to try it and give us feedback on:

- Github: https://github.com/nginx/njs/issues
- Mailing list: http://mailman.nginx.org/mailman/listinfo/nginx-devel

Changes with njs 0.3.6 22 Oct 2019

nginx modules:

*) Improvement: getting special headers from r.headersIn.

Core:

*) Feature: added new Function() support.

*) Feature: added Number.prototype.toFixed().

*) Feature: added Number.prototype.toPrecision().

*) Feature: added Number.prototype.toExponential().

*) Improvement: making "prototype" property of function
instances writable.

*) Improvement: limiting recursion depth while compiling.

*) Improvement: moving global functions to the global object.

*) Bugfix: fixed prototype mutation for object literals.

*) Bugfix: fixed heap-buffer-overflow while parsing regexp literals.

*) Bugfix: fixed integer-overflow while parsing exponent
of number literals.

*) Bugfix: fixed parseFloat().

*) Bugfix: fixed Array.prototype functions according to the
specification.
The following functions were fixed: every, includes, indexOf,
filter,
find, findIndex, forEach, lastIndexOf, map, pop, push, reduce,
reduceRight, shift, some, unshift.

*) Bugfix: fixed handing of accessor descriptors in Object.freeze().

*) Bugfix: fixed String.prototype.replace() when first argument
is not a string.

*) Bugfix: fixed stack-use-after-scope in Array.prototype.map().

*) Bugfix: Date.prototype.toUTCString() format was aligned to ES9.

*) Bugfix: fixed buffer overflow in Number.prototype.toString(radix).

*) Bugfix: fixed Regexp.prototype.test() for regexps with
backreferences.

*) Bugfix: fixed Array.prototype.map() for objects with nonexistent
values.

*) Bugfix: fixed Array.prototype.pop() and shift() for sparse objects.

*) Bugfix: fixed Date.UTC() according to the specification.

*) Bugfix: fixed Date() constructor according to the specification.

*) Bugfix: fixed type of Date.prototype.
Thanks to Artem S. Povalyukhin.

*) Bugfix: fixed Date.prototype.setTime().
Thanks to Artem S. Povalyukhin.

*) Bugfix: fixed default number of arguments expected by built-in
functions.

*) Bugfix: fixed "caller" and "arguments" properties of a function
instance.
Thanks to Artem S. Povalyukhin.
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

High memory usage (no replies)

$
0
0
Hello,

I need your help, I have a problem with my Nginx server : all the Nginx processes are consuming a huge amount of memory and it sets off the OOM Killer.
I don't understand why Nginx uses this much memory, it seems odd, I expected the CPU to be the first problem instead of memory.

My Nginx server is just a reverse proxy, to all kind of backend. SSL can be offloaded or not, it depends on the backend.

I have a huge amount of vhosts with SSL on this Nginx (~15K) and the server have a lot of trafic (for me at least !) .
The /stub_status tell me the following thing at this moment :

Active connections: 3867
server accepts handled requests
2350039 2350039 5489648
Reading: 0 Writing: 332 Waiting: 3605

Netdata (https://github.com/netdata/netdata) tell me that it handle between 300 and 600 req/s.

[root@nginxsrv nginx]# cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)

[root@nginxsrv nginx]# nginx -V
nginx version: nginx/1.17.3
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC)
built with OpenSSL 1.1.0k 28 May 2019
TLS SNI support enabled
configure arguments: --add-module=/usr/local/src/ngx_brotli --add-module=/usr/local/src/kyprizel-testcookie-nginx-module
--with-threads --with-openssl=/usr/local/src/openssl --with-http_v2_module --with-http_flv_module --with-ipv6 --with-http_mp4_module
--sbin-path=/usr/local/sbin --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --error-log-path=/var/log/nginx/error.log
--http-log-path=/var/log/nginx/access.log --with-http_realip_module --with-http_ssl_module --http-client-body-temp-path=/eacc/nginx_client
--http-proxy-temp-path=/eacc/nginx_proxy --http-fastcgi-temp-path=/eacc/nginx_fastcgi --with-http_stub_status_module

The server have a lot of ram, 120G and the CPU is an Intel Xeon E5-2697 CPU. The CPU is not used that much.

A typical vhost file is quite simple, it's just a proxy_pass to a backend, with some hack to do a retry is we first get and error message (based on proxy_intercept_errors). http2 is on. I don't use any caches.

Things I have tested or I suspect to be an issue :
- I reduced the worker_processes to 6. I had issue with the frequent reloading of Nginx with an upper value. I suspect that it's more difficult for Nginx to reload properly if a lot of processes are spawned (correct me if i'm wrong)
- I have gzip on and gzip_proxied to any. I suspect the compression to be an issue, I reduced the buffers value to gzip_buffers 32 4k; and gzip_comp_level to 1
- I reduced the ssl_session_cache from 10m to 1m
- I reduced the keep_alive timeout too (30)
- Reloading Nginx often seems to be a problem too, the memory usage seems higher during the reloading task. The reloading is quite slow too, probably because of the number of vhosts file to load (if someone know how to speed up this, it interest me !)
- I have a lot of limit_conn configuration
- ssl_stapling is off, I had issue with it with the DNS resolution.

Do you have idea on what can cause a high memory usage on Nginx ?

Thanks,
Alexis

Re: [nginx-announce] nginx-1.17.5 (no replies)

$
0
0
Hello Nginx users,

Now available: Nginx 1.17.5 for Windows
https://kevinworthington.com/nginxwin1175 (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.

Announcements are also available here:
Twitter http://twitter.com/kworthington

Thank you,
Kevin
--
Kevin Worthington
kworthington *@* (gmail] [dot} {com)
https://kevinworthington.com/
https://twitter.com/kworthington


On Tue, Oct 22, 2019 at 11:35 AM Maxim Dounin <mdounin@mdounin.ru> wrote:

> Changes with nginx 1.17.5 22 Oct
> 2019
>
> *) Feature: now nginx uses ioctl(FIONREAD), if available, to avoid
> reading from a fast connection for a long time.
>
> *) Bugfix: incomplete escaped characters at the end of the request URI
> were ignored.
>
> *) Bugfix: "/." and "/.." at the end of the request URI were not
> normalized.
>
> *) Bugfix: in the "merge_slashes" directive.
>
> *) Bugfix: in the "ignore_invalid_headers" directive.
> Thanks to Alan Kemp.
>
> *) Bugfix: nginx could not be built with MinGW-w64 gcc 8.1 or newer.
>
>
> --
> Maxim Dounin
> http://nginx.org/
> _______________________________________________
> nginx-announce mailing list
> nginx-announce@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-announce
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

unsubscribing (no replies)

$
0
0
i followed your unsubscribe directions they dont seem to be working on my phone i have been receiving your emails for ever and i never signed up for it no password dont even know what nginx is please make it go awaySent from my T-Mobile 4G LTE Device_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

proxy_store: is it used much? (no replies)

$
0
0
Hello,

proxy_store seems to be a much simpler alternative to “cache" pseudo-static resources. But there is very little discussion of it on the Internet or nginx forum (compared to proxy_cache).

Is there anything non-obvious that speaks agains the use of proxy_store?

Thanks…

Roger

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Don't log 404 error (1 reply)

$
0
0
Hello,

How not to log 404 errors:

2019/10/29 12:42:09 [error] 469#469: *16382 open()
"/var/www/website/fr/telecharger" failed (2: No such file or directory),

In my config I have:

error_log /var/log/nginx/website-error.log;

Because I use 404 for doing url rewriting and so they are not errors...

error_page 404 = /url_rewriting.php;


Thanks,
Vincent.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Input filters in Nginx? (no replies)

$
0
0
Hi all. I did some search on the web and the archives here and did not find an conclusive answer to this question.

Apache has both input a filters (work on the request before content generation) and output filters (work on generated content). As I am exploring the possibility to port some Apache modules that transform data in both directions in a proxy-setup to Nginx, I am wondering whether Nginx has input filters as well. What I have read about Nginx modules seem to indicate that it does not. Is that correct?

I am aware that I could hack something into the proxy module, but I would like to avoid that approach.

Thanks for any insights or pointers.

unknown directive "geoip_country" for openresty/nginx 1.9.7.4 (1 reply)

$
0
0
Hi,

I've run into an issue which is very similar to https://forum.nginx.org/read.php?2,266453,266453#msg-266453, but with a different version such that the solution for that (directive `load_module`) is not available yet.

I am building a docker container of nginx with modsecurity and geoip on Ubuntu Xenial, and I'm stuck with the geoip part as I can't find the instructions for version 1.9.7.4, which doesn't support dynamic module. Can someone please help?

I've tried a few things as in the following:

1. Add `--with-http_geoip_module` as an option for configure

2. `apt-get install ngx_http_geoip_module`, and it returns
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ngx_http_geoip_module

3. Declaring 'load_module "modules/ngx_http_geoip_module.so";' and that is not allowed as the load_module directive is not available in that version

4. Declaring geoip_country /usr/share/GeoIP/GeoIP.dat; results in `nginx: [emerg] unknown directive "geoip_country" ...'

Thank you.

Check if a resource is in the cache (no replies)

$
0
0
Hello,

is there a way to check if a requested resource is in the cache?

For example, “if” has the option “-f”, which could be used to check if a static file is present.

Is there something similar for a cached resource?

Thanks…

Roger

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

only allow abc.com/live/* and abc.com/trial/* (no replies)

$
0
0
Hi,

We would like to use filter to give some protection to backend.
We only want to allow

abc.com/live/* and abc.com/trial/*

I wonder how to achieve this? and can I do better in general?

Content_Length and gzip (1 reply)

$
0
0
Hello, I found if enable gzip, the http header will not include "Content_Length:..." and use "Transfer-Encoding: chunked" instead. But in your home page, "nginx.org" will return both gzip and Content_Length, why? do you use another version for yourself?

Current, nginx.org seem use 1.17.3 version, I have tested with 1.17.3 and 1.17.5. Thanks

Re: TR: Content_Length and gzip (no replies)

$
0
0
Then, we will edit the file /etc/nginx/nginx/nginx.conf
This is what I put in mine :
user www-data;
worker_processes 2;

error_log /var/log/nginx/error.log;
pid /var/run/nginx.pid;

events {
worker_connections 1024;
}

http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
access_log /var/log/nginx/access.log;
server_names_hash_bucket_size 64;
sendfile on;
tcp_nopush on;
#keepalive_timeout 0;
keepalive_timeout 65;
tcp_nodelay on;
gzip on;
gzip_comp_level 5;
gzip_http_version 1.0;
gzip_min_length 0;
gzip_types text/plain text/html text/css image/x-icon application/x-javascript;
gzip_vary on;
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;

I find out, thanks.

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,286079,286080#msg-286080

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
 


 
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Re:(6) Do you want a million for the New Year? (no replies)

$
0
0
This is a text part of the message.
It is shown for the users of old-style e-mail clients

Block spefic URL (no replies)

$
0
0
Hello,
I'm trying to block such kind of URL

https://mysite.com/#id=826c99368cc93a894267703e0fc2ed46

Tried
if ( $request_uri = https://mysite.com/#id=826c99368cc93a894267703e0fc2ed46) {
return 444;
}

location ~* https://mysite.com/#id=826c99368cc93a894267703e0fc2ed46 {
deny all;
}

if ( $query_string = "826c99368cc93a894267703e0fc2ed46" ) {
return 404;
}

No one of this solution didn't help

Git Plugin (no replies)

$
0
0
Hi Everyone,

I'm running a Fedora 31 server. The server hosts one Nginx-based website on 80 and 443. The server also hosts one Git-project. The Git project is located at /var/myproject and only accessible over SSH at the moment.

I'd like to put a web front-end on the Git project for browsing and diff'ing.

Searching the forum I don't see discussions of Git plugins or Nginx front-ends for Git projects.

My question is, does someone have a recommendation for a simple Nginx plugin to put the project on the web?

Thanks in advance.
Viewing all 7229 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>