On Apr 7, 2013, at 0:44 , Jim Ohlstein wrote:
> This way there is no competition for what is listening on IPv6 addresses
> and you should not see that error. I've been doing it this way for at
> least a couple of years now, certainly before 1.0.x series came out. It
> may not be the "recommended"
Thanks Maxim !
There was a misunderstanding there, I thought I shouldn't use the whole
directive, I didn't get that only the 'ipv6only=on' part was not to be
repeated amongst servers.
Works great ('of course it does!' ;o)).
Thanks for the help again,
---
*B. R.*
On Sat, Apr 6, 2013 at 5:25 PM,
Hello!
On Sat, Apr 06, 2013 at 04:05:22PM -0400, B.R. wrote:
> That's exactly what I tried first, and if there are multiple servers
> listening to same ports, I get the following error:
> nginx: [emerg] duplicate listen options for [::]:80 in
> /etc/nginx/conf.d/***.conf:3
You've already been to
On 4/6/13 4:05 PM, B.R. wrote:
> That's exactly what I tried first, and if there are multiple servers
> listening to same ports, I get the following error:
> nginx: [emerg] duplicate listen options for [::]:80 in
> /etc/nginx/conf.d/***.conf:3
> See follow-up messages or (through the forum archive
That's exactly what I tried first, and if there are multiple servers
listening to same ports, I get the following error:
nginx: [emerg] duplicate listen options for [::]:80 in
/etc/nginx/conf.d/***.conf:3
See follow-up messages or (through the forum archive on this subject):
http://forum.nginx.org/
Thank you both of you,
I admit I started worrying on the basis of wrong information/comprehension.
Now it is ok, and I can keep up my nginx config with the x-accel variables.
Thanks again, and sincerely sorry I bothered you for such thing.
Regards,
Larry
Posted at Nginx Forum:
http://forum.n
Hello,I would like to use the FastCGI cache feature of nginx for my web application. But I need to use it only for a set of URL.I would like to use it for the following locations:http://domain.com/index.php?act=detail&ID=[ANY ID HERE]Example:http://domain.com/index.php?act=detail&id=o2ZimgAnd so on
server {
listen 80;
listen [::]:80 ipv6only=on;
server_name one;
...
}
server {
listen 443 ssl;
listen [::]:443 ssl ipv6only=on;
server_name one;
...
}
--
Igor Sysoev
http://nginx.com/services.html
On Apr 6, 2013, at 19:01 , B.R. wrote:
> Add-on:
>
>
Add-on:
Besides, as I explained earlier, having generic 'listen' directives implies
some difficulties.
For example, I am using 2 virtual servers to serve content for the same
server_name, one listening on port 80, the other on port 443, allowing me
to serve cotnent for HTTP and HTTPS in different
But as I noticed earlier, these configuration directives conflict with each
other across multiple virtual servers...
That's a huge step backwards.
H
aving to specify them only once across every configuration file is
counter-intuitive.
Why isn't nginx able to summarize all the needs for listening
On 6 April 2013 15:27, Larry wrote:
> Reassuring but everywhere on the web, you can see wireshark sniffing in/out
> packet to any server.
No you can't.
> Hence, they are not connected to the server to sniff packets.
Your conclusion is wrong as it is based on incorrect information.
> That is wh
Reassuring but everywhere on the web, you can see wireshark sniffing in/out
packet to any server.
Hence, they are not connected to the server to sniff packets.
That is why I started worrying actually !
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238162,238166#msg-238166
__
any hacker will need to be inside your server or have some
administration over the network to find those ips
On 06/04/13 15:01, Larry wrote:
My concern is that a hacker is able to know my other ips over europe.
My host is not a problem. The real deal is the outgoing packets I don't want
extern
My concern is that a hacker is able to know my other ips over europe.
My host is not a problem. The real deal is the outgoing packets I don't want
external people to know where they are going to.
It would defeat the whole purpose of reverse proxy..
Posted at Nginx Forum:
http://forum.nginx.org/
If you run wireshark on your main box, you will be able to see the ips
it connects to (but not the urls because of https). However they would
need to be logged into your box to run wireshark and at this point they
could just run a netstat command to find the ips it is connected to.
If you mean c
Hello,
I am suddenly worrying about something simple :
I have a box that send some traffic with proxy_pass to get files from
another of my box faking the url. Hence acting as a reverse proxy.
All the connections are ssl covered.
Right.
But is the whole reverse proxy broken if one listen with w
Hello!
On Sat, Apr 06, 2013 at 02:25:54AM -0400, B.R. wrote:
> Hello,
>
> It seems I solved the problem...
> It was indeed by reading a little more carefully the doc
> http://wiki.nginx.org/HttpCoreModule#listen, thanks @Lukas! ;o)
>
> The '*:80' syntax is used for IPv4 listening, I don't under
17 matches
Mail list logo
