On Tue, Jul 09, 2013 at 09:11:56AM -0400, Peleke wrote:
Hi there,
> Yes, you are right. Such a small change!
Yes. nginx and wordpress do tend to work well together, so "typical"
fixes are usually straightforward.
> Thanks a lot and sorry for taking such a long time. Next time I know how to
> p
Yes, you are right. Such a small change!
Thanks a lot and sorry for taking such a long time. Next time I know how to
post a proper question.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240504,240687#msg-240687
___
nginx mailing list
nginx
On Mon, Jul 08, 2013 at 03:42:31PM -0400, Peleke wrote:
Hi there,
> http://www.peleke.de/galerie/google/
> Nothing happens after a click on an album thumbnail. You will only see a
> reload of the page and this added to the URL:
> ?page_id=0&albid=5898003541337462625 (for example) which should sho
on;
tcp_nopush on;
tcp_nodelay on;
types_hash_max_size 2048;
send_timeout 2;
client_max_body_size 20m;
client_body_buffer_size 128k;
client_body_timeout 10;
client_header_timeout 10;
keepalive_timeout 10;
open_file_cache max=
On Sun, Jul 07, 2013 at 04:27:23PM -0400, Peleke wrote:
Hi there,
> Sorry but my last message was delayed, may be you didn't see it but the
> problem is still not solved and it worked before with Apache. I would be
> happy if you could help me, thanks!
>From all of the words you have written so
Sorry but my last message was delayed, may be you didn't see it but the
problem is still not solved and it worked before with Apache. I would be
happy if you could help me, thanks!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240504,240630#msg-240630
_
The problem still exists. You can only see the album thumbnails but it
should be possible to click on them to see all pictures from an album and
then see them in full screen.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240504,240594#msg-240594
___
No, the problem is not solved: You can see the album thumbnails but when you
click on them there should be a page with the different pictures from that
album which you can view in full screen mode.
You can see how it should work on http://wp.oopstouch.com/?page_id=22 and I
think the problem is rel
On 3 July 2013 23:17, Francis Daly wrote:
> On Wed, Jul 03, 2013 at 09:45:44AM -0400, Peleke wrote:
>
>> Try Flickr or Google+ instead, that error message isn't related to the
>> problem I mentioned, sorry.
>
> Good news! I see no evidence of the nginx-related problem that you have
> described, on
On Wed, Jul 03, 2013 at 09:45:44AM -0400, Peleke wrote:
> Try Flickr or Google+ instead, that error message isn't related to the
> problem I mentioned, sorry.
Good news! I see no evidence of the nginx-related problem that you have
described, on either of those two pages, so I presume that you fix
Try Flickr or Google+ instead, that error message isn't related to the
problem I mentioned, sorry.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240504,240539#msg-240539
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman
On Tue, Jul 02, 2013 at 08:16:00PM -0400, Peleke wrote:
Hi there,
> Sorry, maybe it is only related to the permalink structure which worked with
> Apache before server move.
Could be; the fact that this is a new nginx deployment which used to be
an apache deployment is probably useful informati
Sorry, maybe it is only related to the permalink structure which worked with
Apache before server move.
The gallery script adds it own extensions to the address.
You can see it live on www.peleke.de/galerie and then click on one of the
three gallery sources (Flickr, Facebook or Google+).
Can you
On Tue, Jul 02, 2013 at 05:24:15PM -0400, Peleke wrote:
Hi there,
> I have set the open_file_cache variable to max=5000 inactive=20s so that it
> is enabled globally but now I want to disable all caching for a specific
> virtual location on a domain:
http://nginx.org/r/open_f
I have set the open_file_cache variable to max=5000 inactive=20s so that it
is enabled globally but now I want to disable all caching for a specific
virtual location on a domain:
- open_file_cache max=5000 inactive=20s;
-- location ^~ /gallery {
open_file_cache off;
}
Sadly
Hello!
On Mon, Apr 15, 2013 at 08:08:20PM +0100, Richard Kearsley wrote:
> Hi
> Is the max value specified in `open_file_cache` on a per-worker basis?
> e.g. if I set it to 20,000, will it cache 80,000 open fds with 4 workers?
Yes, it's per-worker.
--
Maxim Dounin
http:
Hi
Is the max value specified in `open_file_cache` on a per-worker basis?
e.g. if I set it to 20,000, will it cache 80,000 open fds with 4 workers?
Thanks
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
17 matches
Mail list logo
