On Tue, May 31, 2016 at 04:48:19PM -0400, Larry Martell wrote:
> On Tue, May 31, 2016 at 4:19 PM, Francis Daly wrote:
> > On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
Hi there,
> > It sounds like your design is that your client sends a http request to
> > port 8004; the http se
Hi folks
OpenResty 1.9.7.5 is just out to include the latest official NGINX
patch for nginx security advisory (CVE-2016-4450):
https://openresty.org/en/download.html
Both the (portable) source code distribution and the Win32 binary
distribution are provided on this Download page.
Changes si
On Tue, May 31, 2016 at 4:19 PM, Francis Daly wrote:
> On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 11:38 AM, Francis Daly wrote:
>> > On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
>
> Hi there,
>
>> >> The C++ app sends the request di
On Tue, May 31, 2016 at 07:04:30PM +0500, Muhammad Yousuf Khan wrote:
Hi there,
> When i scan my site with builtwith.com it is showing that i am using both
> nginx and apache.
When you scan your site with builtwith.com, what do your nginx logs say
the requests were?
When you make those same req
On Tue, May 31, 2016 at 12:33:56PM -0400, Larry Martell wrote:
> On Tue, May 31, 2016 at 11:38 AM, Francis Daly wrote:
> > On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
Hi there,
> >> The C++ app sends the request directly to port 8000. With the django
> >> app a request is sent
Hello Nginx users,
Now available: Nginx 1.11.1 for Windows
https://kevinworthington.com/nginxwin (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
Hello Nginx users,
Now available: Nginx 1.10.1 for Windows
https://kevinworthington.com/nginxwin1101 (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
Hello!
A problem was identified in nginx code responsible for saving
client request body to a temporary file. A specially crafted request
might result in worker process crash due to a NULL pointer dereference
while writing client request body to a temporary file (CVE-2016-4450).
The problem affe
Changes with nginx 1.10.131 May 2016
*) Security: a segmentation fault might occur in a worker process while
writing a specially crafted request body to a temporary file
(CVE-2016-4450); the bug had appeared in 1.3.9.
--
Maxim Dounin
htt
Changes with nginx 1.11.131 May 2016
*) Security: a segmentation fault might occur in a worker process while
writing a specially crafted request body to a temporary file
(CVE-2016-4450); the bug had appeared in 1.3.9.
--
Maxim Dounin
htt
On Tue, May 31, 2016 at 11:38 AM, Francis Daly wrote:
> On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 9:45 AM, Francis Daly wrote:
>
> Hi there,
>
>> > Possibly one of them covers what you want?
>>
>> There are 2 ways requests get to port 8000, which is
It seems the lock lies in the fact there is no generic way for the listen
directive to specify multiple ports, so you are stuck with that much server
blocks.
Now, you could use the $server_port variable in the proxy_pass directive,
but that brings no real improvement.
You could use configuration
On Tue, May 31, 2016 at 10:26:26AM -0400, Larry Martell wrote:
> On Tue, May 31, 2016 at 9:45 AM, Francis Daly wrote:
Hi there,
> > Possibly one of them covers what you want?
>
> There are 2 ways requests get to port 8000, which is the port I want
> to check headers on.
>
> One is via a C++ Qt
Thanks a lot for the fast response!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267240,267249#msg-267249
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tue, May 31, 2016 at 9:45 AM, Francis Daly wrote:
> On Tue, May 31, 2016 at 09:23:36AM -0400, Larry Martell wrote:
>> On Tue, May 31, 2016 at 7:55 AM, Larry Martell
>> wrote:
>> >>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
>> >>> wrote:
>
> Hi there,
>
>> Is there any way with ng
When i scan my site with builtwith.com it is showing that i am using both
nginx and apache. however i have completely moved my site from apache to
nginx. Though previously it was on Apache which i uninstalled after
installing nginx.
Now i am woundering why its showing both.
i check netstat its s
On Tue, May 31, 2016 at 09:23:36AM -0400, Larry Martell wrote:
> On Tue, May 31, 2016 at 7:55 AM, Larry Martell
> wrote:
> >>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
> >>> wrote:
Hi there,
> Is there any way with nginx to check a request's headers and send back
> a 401 if th
On Tue, May 31, 2016 at 7:55 AM, Larry Martell wrote:
> On Tue, May 31, 2016 at 7:41 AM, Larry Martell
> wrote:
>> On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
>> wrote:
>>>
>>>
>>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
>>> wrote:
Is there any way with nginx to check a
Hello!
On Tue, May 31, 2016 at 07:12:20AM -0400, mastercan wrote:
> Hello folks,
>
> I have the following setup:
> Nginx 1.11.0
> Libressl 2.3.4
>
> 1 Letsencrypt RSA 2048 certificate
> 1 Letsencrypt ECDSA p256 certificate
>
> The certificate files are both chained. Both have the Letsencrypt R
On Tue, May 31, 2016 at 7:41 AM, Larry Martell wrote:
> On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
> wrote:
>>
>>
>> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
>> wrote:
>>>
>>> Is there any way with nginx to check a request's headers and send back
>>> a 401 if the headers are not pro
On Mon, May 30, 2016 at 2:19 PM, Robert Paprocki
wrote:
>
>
> On Sat, May 28, 2016 at 12:48 PM, Larry Martell
> wrote:
>>
>> Is there any way with nginx to check a request's headers and send back
>> a 401 if the headers are not proper?
>
>
>
> Yes, you can do with this via the 'map' and 'if' dire
Hello folks,
I have the following setup:
Nginx 1.11.0
Libressl 2.3.4
1 Letsencrypt RSA 2048 certificate
1 Letsencrypt ECDSA p256 certificate
The certificate files are both chained. Both have the Letsencrypt RSA 2048
X3 intermediate certificate at the end of the file.
The problem is:
Nginx retur
I have this configure file, but it is long-winded。
in nginx, are there having one expression to handle it
server {
listen 192.168.1.2:1;
proxy_pass 192.168.0.3:1;
}
server {
listen 192.168.1.2:10001;
proxy_pass 192.168.0.3:10001;
}
23 matches
Mail list logo
