Hi,
if you use unix/linux severs with root access you can use
tcpdump -i $interface port 443
Regards, Axel
Am Donnerstag, 5. Februar 2015, 00:08:10 schrieb exilemirror:
> Hi guys,
>
>
> I have a site configured to run on port 443 only, where can we see if the
> request coming in are using p
Hi guys,
I have a site configured to run on port 443 only, where can we see if the
request coming in are using port 443 instead of port 80?
Can we capture the traffic live?
Thank you.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256458,256458#msg-256458
___
On Wed, Feb 04, 2015 at 11:36:04PM +0200, peter petrov wrote:
> In my previous post I explained what tried and didn't manage to it. I
> attached nginx.conf file. I'll
> be very grateful is somebody show me a successful way to do this.
http://nginx.org/r/gzip_static
gzip_static on;
curl -i
Hi folks!
I am happy to announce the new formal release, 1.7.7.2, of the OpenResty bundle:
http://openresty.org/#Download
The highlights of this release are
1. the SSL/TLS support in the websocket client of lua-resty-websocket.
2. an enhanced version of "resty" command-line utility support
In my previous post I explained what tried and didn't manage to it. I
attached nginx.conf file. I'll
be very grateful is somebody show me a successful way to do this.
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/
it's ok.
I guess it works like that without moving the access_log directive.
so I have the set $request_id directive in the server section, and then
it is used properly afterwards in the http section.
thank you!
On 2/4/2015 11:22 AM, Igal @ getRailo.org wrote:
> thank you for your prompt reply
thank you for your prompt reply.
yes, it works in the server section, but my access_log is in the http
section, and I want to use it in the access_log
should I just add
*access_log* |off|;
in the http section and add the access_log to the server section instead?
thanks
On 2/4/2015 11:15
On Wed, Feb 04, 2015 at 11:07:13AM -0800, Igal @ getRailo.org wrote:
Hi there,
> I want to be able to identify requests by a unique id.
>
> I'm able to do this in the location section:
>
> proxy_set_headerX-Request-Id
> $pid-$msec-$remote_addr-$request_length;
>
> but I wan
hi,
I want to be able to identify requests by a unique id.
I'm able to do this in the location section:
proxy_set_headerX-Request-Id
$pid-$msec-$remote_addr-$request_length;
but I want instead to set it to a variable, e.g. in the http section:
set $request_id $pid-$msec
Nothing in the configuration part you provided rings any bell to me on why
this is going on.
I suggest you take a deeper look at the server level, see if there is not
something that might have an impact there.
Also, the usual recommended process to seek for the source of the trouble
is to find wha
jtan,
The connection is encrypted using AES_256_CBC, with SHA1 for message
authentication and ECDHE_RSA as the key exchange mechanism.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256386,256442#msg-256442
___
nginx mailing list
nginx@nginx
B.R.
They are serving exactly the same resources at the same time... My vhost
points to the same folders for each domain. Files are accessible over HTTP
and HTTPS. The slow down comes when downloading (the same resource) from
HTTPS. For example:
http://webmail.domain.tld/test.zip (30MB file can
On 04 Feb 2015, at 12:11, justink101 wrote:
> Is it possible to specify multiple proxy_pass destinations from a single
> location block? Currently we have:
>
> location ~ ^/v1/?(?.+)? {
>resolver 208.67.222.222 208.67.220.220 valid=300s;
>resolver_timeout 10s;
>proxy_intercept_errors
Is it possible to specify multiple proxy_pass destinations from a single
location block? Currently we have:
location ~ ^/v1/?(?.+)? {
resolver 208.67.222.222 208.67.220.220 valid=300s;
resolver_timeout 10s;
proxy_intercept_errors off;
proxy_hide_header Vary;
proxy_set_header Ho
14 matches
Mail list logo
