https://mailman.nginx.org/pipermail/unit/2021-November/000288.html
Thank you again for keeping your finger on the pulse, reporting issues and
submitting feature requests via our GitHub issue tracker:
- https://github.com/nginx/unit/issues
Stay tuned!
en
reconfigured.
*) Bugfix: fixed building with glibc 2.34, notably Fedora 35.
Other major features that we are preparing for the next release include:
- basic statistics API for monitoring Unit instances
- various variables for different aspects of request and connection data
- customization of access log format with variables
- custom variables out of regexp captures on various request parameters
- simple request rewrite using variables
- command-line tool to simplify the use of Unit's control socket API
There probably will be even more.
To participate, share your ideas, or discuss new features, you're welcome
to visit Unit's issue tracker on GitHub:
- https://github.com/nginx/unit/issues
Stay tuned!
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ites using variables
- More variables to access request and connection information
- A statistics API
- Unit CLI utility tool
- App prototype processes to reduce memory usage, share the PHP opcache,
and improve the handling of apps isolation
- njs integration (https://nginx.org/en/docs/njs/index.html)
- .NET Core language module prototype
Some of them bound to appear in the next release. Stay tuned!
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
;auto_globals_jit" option
enabled.
That's all for today, but even more exciting features are poised for the
upcoming releases:
- statistics API
- process control API
- variables from regexp captures in the "match" object
- simple re
fun videos
instead of reading tedious documentation, I'm happy to recommend Timo Stark,
our own PM Engineer. Recently, he started regularly streaming on Twitch and
YouTube:
- https://www.twitch.tv/h30ne
- https://www.youtube.com/Tippexs91
Tomorrow (March 26), at 10 p.
mprovements to process isolation.
As always, we encourage you to follow our roadmap on GitHub, where your
ideas and requests are more than welcome:
- https://github.com/orgs/nginx/projects/1
Stay tuned!
wbr, Valentin V. Bartenev
___
nginx maili
//www.freshports.org/www/unit/
We encourage you to follow our roadmap on GitHub, where your ideas and requests
are always more than welcome:
- https://github.com/orgs/nginx/projects/1
Stay tuned!
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
s.com/NGINX/job/Cork-NGINX/Software-Engineer_RP1018735
More information about the project: https://unit.nginx.org/
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
route matching patterns
to support regular expressions; working on keepalive connection caching;
adding multithreading to application modules; and finally, fabricating the
metrics API!
We encourage you to follow our roadmap on GitHub, where your ideas and requests
are always m
Isolation in NGINX Unit
https://www.nginx.com/blog/filesystem-isolation-nginx-unit/
Stay tuned!
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
quests between them using various sophisticated request matching rules.
Check our website to know more about the new option:
- https://unit.nginx.org/configuration/#targets
To learn more about request matching rules:
- https://unit.nginx.org/configuration/#condition-matching
applications.
*) Bugfix: broken build on DragonFly BSD; the bug had appeared in
1.16.0.
Please also see a blog post about the new features of our two previous releases:
- https://www.nginx.com/blog/nginx-unit-1-16-0-now-available/
To keep the finger on the pulse, refer to our further plans in the roadmap here:
- https://github.com/orgs/nginx/projects/1
Stay healthy, stay home!
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
*) Bugfix: compatibility issues with some Python applications.
To keep the finger on the pulse, see our further plans in the roadmap here:
- https://github.com/orgs/nginx/projects/1
Also, good news for macOS users! Now, there's a Homebrew tap for Unit:
- https://unit.nginx.org/installation/#homebrew
Stay healthy!
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
quot;try_files"-like functionality for more sophisticated request routing.
Stay tuned!
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
epared Docker images and packages
- Maxim Romanov - senior developer, who worked on Java, WebSockets,
and internal IPC
- Tiago Natel de Moura - senior developer, who worked on isolation features
Thank you guys, I'm happy to work with you.
wbr, Valentin V. Bartene
on, please?
> Why is it so hard to reply to a post?
>
> Thanks.
>
The digest mode in mailing lists is usually suited only if you want to
receive "latest news" and don't want to participate in discussions.
Otherwise you should subscribe in normal mode.
wbr, Valen
t mailing list:
- https://mailman.nginx.org/mailman/listinfo/unit
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ation
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ocket server implementation for Java Servlet
Containers.
*) Feature: direct addressing of API configuration options containing
slashes "/" using URI encoding (%2F).
*) Bugfix: segmentation fault might have occurred in Go applications
under high load.
*) Bugfix:
ish the first round of adding basic
support for serving static media assets and proxying in Unit.
Stay tuned!
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
it more time.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ia assets.
Stay tuned, give feedback, and help us to create the best software ever.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
affects Unit 0.3 - 1.7.
The issue is fixed in Unit 1.7.1.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
bug had appeared in 1.7.
Release of Unit 1.8 with support for internal request routing and an
experimental Java module is planned for end of February.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman
://github.com/mar0x/unit
, so everybody willing to run their Java applications on Unit can participate.
Many other good things and announcements about Unit will surely happen in 2019.
Thank you for staying with us, and all the best.
wbr, Valentin V. Bartenev
__
On Wednesday 12 December 2018 19:11:59 Ralph Seichter wrote:
> * Valentin V. Bartenev:
>
> > http://hg.nginx.org/unit/rev/fd323ad9e24f
>
> That looks promising, Valentin. I'll try a build as soon as I'm able
> to. Would you perhaps consider releasing this as
On Sunday 09 December 2018 21:14:14 Valentin V. Bartenev wrote:
> On Sunday, 9 December 2018 16:41:56 MSK Ralph Seichter wrote:
> > Hello developer team.
> >
> > I am the maintainer of the NGINX Unit ebuild for Gentoo Linux, and
> > currently I am struggling with colli
l, especially for Gentoo.
I think you can just remove it.
See also this overlay for some ideas:
https://github.com/msva/mva-overlay/tree/master/www-servers/nginx-unit
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ke a look at the existing njs
modules for nginx: http://hg.nginx.org/njs/file/tip/nginx
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
rnal_ resources. The js module just provides you an API
for this mechanism to make ssi-like subrequests.
You're looking for a different thing, in fact you need an http client in the
js module to request external resources. That's not something provided right
now, but will be nice to have
of pool" alerts might have appeared in
log.
*) Bugfix: module discovery didn't work on 64-bit big-endian systems
like IBM/S390x.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
if (n == svcs.length) {
r.return(403);
return;
}
r.subrequest("/" + svcs[n++], '', done);
}
callNextService();
}
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
re run in parallel:
http://nginx.org/en/docs/njs/examples.html#fast_response
If you want to schedule the second subrequest only after the first one is
finished, then simply put your second subrequest call inside the done
callback of the first one.
wbr, Va
e.
>
[..]
njs implements "strict mode" of JS:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode
It's said in the beginning of documentation: http://nginx.org/en/docs/njs/
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
cing "last message send failed: Resource temporarily
unavailable" alerts in log; the bug had appeared in 1.4.
*) Bugfix: Go applications didn't work when Unit was built with musl C
library.
wbr, Valentin V. Bartenev
___
ngin
y-grade documentation for Unit. You are welcome to join
this effort with your ideas, suggestions, and edits: just send a pull request
or open an issue in our documentation repository on GitHub:
- https://github.com/nginx/unit-docs/
Stay tuned!
wbr, Valentin V. Bartenev
_
mple are
set to their default values. So, there's no need to set them explicitly
if you are happy with the values above.
Binary Linux packages and Docker images are available here:
- Packages: https://unit.nginx.org/installation/#precompiled-packages
- Dock
rent
implementation the client connection is kept "busy" during background
update and the last chunk may rest in the socket until kernel will send
it.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
every minute, showed an increase in
> response time following this change.
>
> After some investigating I pinned it down to a ~200 ms delay coming from
> using proxy_cache_background_update.
>
[..]
I assume you have tcp_nopush directive enabled, then please try switching it
off.
> fastcgi_cache, based ...
>
Like almost all official modules, it's independent from the protocol used.
http://nginx.org/r/proxy_cache_purge
http://nginx.org/r/fastcgi_cache_purge
http://nginx.org/r/uwsgi_cache_purge
http://nginx.org/r/scgi_cache_
GINE": "django.db.backends.postgresql_psycopg2",
"DB_NAME": "mydb",
"DB_HOST": "127.0.0.1"
}
}
}
Please note that "environment" can be configured for any type of application.
Binary Linux packages and Docker images are available here:
- Packages: https://unit.nginx.org/installation/#precompiled-packages
- Docker:https://hub.docker.com/r/nginx/unit/tags/
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
nitd is executed) or in the application code.
Also, you can pass custom data from nginx using headers.
Setting environment variables through API is planned for the next release
in June.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.o
"path": "/var/www/myapp",
"home": "/path/to/your/venv/directory"
}
Please also note that your application callable need to be named
"application" (not "app"). That can be easily achievable by:
application = app
in your wsgi.py
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
e any ideas for improvements,
please feel free to share here:
- Mailing list: http://mailman.nginx.org/mailman/listinfo/unit
- GitHub: https://github.com/nginx/unit/issues
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://ma
If you wish to know more
about the project and our plans, please read the announcement blog post:
- https://www.nginx.com/blog/nginx-unit-1-0-released/
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
mages are available here:
- Packages: https://unit.nginx.org/installation/#precompiled-packages
- Docker:https://hub.docker.com/r/nginx/unit/tags/
Packages and images for the new Ruby module will be built next week.
wbr, Valentin V. Bartenev
___
"processes": 10,
> "module": "wsgi",
> "user": "root",
> "group": "root",
> "path": "/var/www/app"
> }
> }
> }
Since your Python application() callable is inside the
/var/www/app/index.py file, then your module should
be called "index", not "wsgi".
See the Python documentation about how it works:
https://docs.python.org/3/tutorial/modules.html#the-module-search-path
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tuesday 13 March 2018 12:43:10 avpdnepr wrote:
> root@instance-1:~# ls -l /var/www/app
> total 0
> root@instance-1:~#
>
So, you have no Python application in /var/www/app.
What are you trying to run then and where it is?
wbr, Valentin
;www-php",
> "root": "/var/www",
> "index": "index.php"
> },
> "cart": {
> "type": "python",
> "processes": 10,
> &
code 1
> 2018/03/13 12:10:37 [warn] 1632#1632 failed to start application
> "example_python"
>
This means that Python interpreter is unable to load your application.
You should check that the path is correct and Unit application process
threads number to one in Windows?
>
[..]
nginx currently cannot use more than one thread in Windows for all operations.
Support for thread pool means adding support for more threads. Moreover, thread
pools in nginx are used only for reading and writing files. They are never used
for connect
cation defined in the config file?
>
Because nginx needs to log errors that happen before the config file
is parsed.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ial Docker containers. See the links
below for details:
- Packages: https://unit.nginx.org/installation/#precompiled-packages
- Docker:https://hub.docker.com/r/nginx/unit/tags/
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
rd points to the right server?
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
- https://www.nginx.com/blog/unit-0-3-beta-release-available-now/
Besides that, please welcome Alexander Borisov who's joined our Unit dev
team today. His first task is going to be adding Perl/PSGI support.
wbr, Valentin V. Bartenev
___
nginx mai
do wrong or what is the "special" configuration
> to use SNI with shared IPv4 address.
>
[..]
Are you sure that a tool you're using to check supports SNI?
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
mplaining about a
> similar thing below.
[..]
What's in the error log?
The error log from one of your links suggests, that the problme in
uwsgi server, not in nginx:
2015/08/25 15:28:49 [error] 10#0: *103 readv() failed (104: Connection reset by
peer) while reading upstream
wbr, Vale
on/#precompiled-packages
Also, here is a new blog post about some of our plans for the near future:
- https://www.nginx.com/blog/nginx-unit-progress-and-next-steps/
Happy New Year and best wishes from all of the Unit team.
Stay tuned.
wbr, Valentin V. Bartenev
___
y personal opinion, the HTTP/2 specification (and the protocol
itself) is a bad example. Some aspects of the protocol are pure
overengineering, some of them are ugly hacks, some of them are just
complexity without any benefits, and some of them are vectors of DoS
attack.
I also suggest to read
On Tuesday, 7 November 2017 18:02:44 MSK Valentin V. Bartenev wrote:
> On Tuesday, 7 November 2017 14:36:47 MSK yang chen wrote:
> > Thank you very much, but there is another question, if delta larger than
> > 1ms, it will invole the ngx_event_expire_timers, why not 2ms or others?
red.
The function triggers all the timers with absolute time less or equal than
the current time. This delta check is just an optimization.
I suggest you to read the code of the function. It's hard to understand the
logic, if you read only the part of it and don't have the whole pic
n 500 rps, which can only indicate blocking issue
or overload.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
own directive "gzip" in
> /usr/local/apps/nginx/etc/conf.d/gzip.conf:2*
>
[..]
You should check your full configuration. It's unclear where this "gzip"
directive is included.
Please note, there's no such directive in mail and stream modules.
wbr, Valentin
t_upstream directives.
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_next_upstream
| off
| disables passing a request to the next server.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Despite the alerts, the access log shows the clients with a 101 status code.
>
> Any idea if this is something on my end I should start looking at, or is
> this a possible issue with http2 and websockets?
>
[..]
Websockets cannot work over HTTP/2.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ndering if anyone
> could explain why it is happening or has a similar problem.
>
> Thank you!
>
Have you checked error log?
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
e, but it
> did not helped.
>
> Any suggestion in this regards will help.
>
> *Version:* nginx-1.10.1-1.el6
>
[..]
First of all, you should update nginx to an actual and supported version:
1.13.5 or 1.12.1.
There's a big chance that your problem was alrea
that we had to add in order to support Chrome:
http://hg.nginx.org/nginx/rev/8df664ebe037
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
you to use tcpdump for investigation and something simple, like curl
as a client.
The network debug window in chrome is a toy that doesn't show you real picture.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Monday 25 September 2017 22:14:04 Valentin V. Bartenev wrote:
> On Monday 25 September 2017 07:17:08 garyc wrote:
> > Apologies, I posted this issue to the wrong list (php-fpm), the link is:
> >
> > > https://forum.nginx.org/read.php?3,276451,276475#msg-276475
> &
@16
2017/09/21 12:09:31 [debug] 22090#0: *60 event timer del: 22: 1505995796403
2017/09/21 12:09:31 [debug] 22090#0: *60 http process request line
Here's a new request received in different connection #60.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
es, modules, filter modules, and so on. The HTTP/2 module works quite
straightforward, if it sees the end of buffer chain in nginx, it adds the
END_STREAM flag. Otherwise, it doesn't.
So, whether you see END_STREAM in a separate DATA frame or not depends on
many factors and your con
lue.
[..]
The fix for RFC would be to allow 405 without "Allow" header.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
x27;s
definitely not the goal you should achieve by any price.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
> nginx doesn't seem to have Allow header field. Is that against RFC?
>
Please, look at the explanations in https://trac.nginx.org/nginx/ticket/1161
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
supported version.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
BUF options are inherited from the
listening socket.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ds up buffering 12.5MB data?
>
You should check tcpdump (or wireshark) to see where actually 12.5MB
of data have been stuck.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
immediately to write socket buffer in kernel
for client connection.
4. Write socket buffer in kernel for client connection where nginx
writes data.
5. Read socket buffer in kernel for client connection from what wget
reads data.
wbr, Valentin V. Bartenev
__
> Thanks!
>
This is very old version of nginx. First of all, you should update up to
the supported version. There are a bunch of bugs have been fixed.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Thursday 29 June 2017 15:32:21 ST wrote:
> On Thu, 2017-06-29 at 15:09 +0300, Valentin V. Bartenev wrote:
> > On Thursday 29 June 2017 14:00:37 ST wrote:
> > > Hello,
> > >
> > > with your help I managed to configure nginx and our website now can be
>
How do I measure its performance and compare it to that
> of apache? Which tools would you recommend?
>
> Thank you in advance!
>
I suggest wrk.
https://github.com/wg/wrk
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
header presents in request).
See the "Parameters Passed to a FastCGI Server" paragraph here:
http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#parameters
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
t;
> Thanks.
>
http://nginx.org/en/linux_packages.html
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
> I really think that nginx should reconsider its position on this matter.
>
> In the meantime, where can I find documentation on how to configure
> proxy_pass to use HTTP/2?
>
There's no such documentation since HTTP/2 isn't supported by the proxy
module.
wbr, Valenti
trol.html#logs
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
exceeded. It would possibly
> save some CPU cycles needed to handle SSL handshake, etc.
>
> Is it possible?
>
You should use system firewall. Most of *nix systems have one out of the box.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
not seem to have any effect. (Why is that so?)
>
[..]
The answer to your question is likely in the parts of the configuration
that you've skipped.
Please note, that the "index" directive produces internal redirects.
In the second case, it looks like your request is redirected t
use all cpu cores and disable
accept_mutex.
You can find more information in this talk:
https://www.youtube.com/watch?v=eLW_NSuwYU0
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ter sending the response.
>
> Any solution for this?
>
That's how the FastCGI protocol works.
--
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tuesday 22 November 2016 08:02:37 Phani Sreenivasa Prasad wrote:
> Hi
>
> So, how can I read this value from my fastcgi app for each request/response?
>
[..]
You can read it from the access_log file.
wbr, Valentin V. Bartenev
___
n
504 /404.html;
> location = /404.html {
> root error;
> }
>
> }
>
> }
>
> Any idea's on how to catch requests to the upstream server?
>
[..]
The configuration above doesn't look like a valid one due to
invalid "add_header" directive.
Your nginx cannot load it.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I was wondering if this is a problem for pipelined HTTP
> requests.
No, there's no such problem with pipelined requests.
Pipelined requests are processed sequentially one by one, nginx quits before
starting processing the next request.
wbr, Valentin V. Bartenev
_
r: amfes.com, request: "HEAD / HTTP/1.0"
>
> Clients I control have no problem reaching the root or the robots.txt
> file - so what is this telling me?
>
The official nginx build cannot produce such messages. They likely come
from 3rd-party module or patches you're usi
ny public DNS in the
resolver
directive: http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver
| To prevent DNS spoofing, it is recommended configuring DNS servers in a
properly
| secured trusted local network.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
nefficient (if-being evil) than
> hard-coding the port and having two different server{} blocks for http and
> https .
>
[..]
Why don't use map?
map $scheme $port {
http ;
https 4430;
}
proxy_pass $scheme://127.0.0.1:$port;
wbr, Valentin V. Bartenev
s idle (cpu usage is zero).
> Why ? is it some kind of limit for nginx on Windows ? Many thanks !!!
http://nginx.org/en/docs/windows.html#known_issues
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
0.1 would support OpenSSL 1.0.2i. Has anyone
> tried this approach before ?
>
http://mailman.nginx.org/pipermail/nginx/2016-September/051914.html
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ore the current one is completely done (by done I mean the
> complete Content-Length is transferred to the client side)?
>
No, it's not possible.
As already were said twice, nginx dosn't support pipelining on the upstream
side.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ll
> correctly ?
[..]
There's no "js_run" directive. Check the README.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
1 - 100 of 507 matches
Mail list logo