Hello!
On Tue, Jan 29, 2013 at 06:49:46PM +0100, Peter Wu wrote:
[...]
> RFC: this patch only adds support for URL parameters. Before implementing the
> actual clickable headers I would like to have some feedback. Do you actually
> want to add such a sorting feature to the standard autoindex mo
Hi,
Thank you for your feedback.
On Wednesday 30 January 2013 21:50:57 Maxim Dounin wrote:
> Overrall I tend to think that it's bad idea to do autoindex more
> customizable. I would rather like to see it producing XML and
> hence any customization being possible with XSLT filter.
Do you want
On Tuesday 29 January 2013 21:49:46 Peter Wu wrote:
> Based on Apache HTTPD autoindex docs[1]. Supported:
> - C=N sorts the directory by file name
> - C=M sorts the directory by last-modified date, then file name
> - C=S sorts the directory by size, then file name
> - O=A sorts the listing in Ascen
Hello!
On Wed, Jan 30, 2013 at 03:50:39AM +, 彭谦(研六 福州) wrote:
> Hello all!
>Recently I came across a problem that CPU 100% when nginx upstream were
> trying to SSL handshake to the web sever.
>the pass_proxy url is
> https://www.salesforce.com/export/login-messages/common/css/images
On Wednesday 30 January 2013 22:54:29 Valentin V. Bartenev wrote:
> I would prefer something like "autoindex_sort" directive
>
> autoindex_sort criterion [ order ];
>
> with variables support.
>
> And if user want Apache-like behavior then he will be able to configure
> it like this:
>
> ma
Ive been working on my first nginx module (well more specifically, a fork
of an existing module with permission).
Pretty close to done however found one thing thats lacking in the nginx
core (as far as I can tell). UDP Listening.
There is support for UDP sockets, so sending of UDP data is fine. H
