Hey all,
I wanted to enforce an SLA on certain http requests to apache.
Essentially provide a the external client users an guarantee that a
valid response will be given within XXms and all errors are
suppressed. This is for an ReST API that returns JSON or XML data.
Ronald Park attempted to do s
Hi Eric.
NOOWWW I understood !!!
But happen a error !!
I posted this error.
Help me
Thank you
Ricardo
Eric Covener wrote:
>
> On Mon, Jul 13, 2009 at 10:06 AM, ricardo13
> wrote:
It's difficult. I'd suggest finding a way to use existing modules.
>>>
>>> Use or modify, that is.
>>> Ca
Hi,
I have a webcluster and I'm prioritize the requests.
I modify request_rec adding a field called prior and conditional test ( IF()
) in mod_rewrite for classify.
All time that start APACHE show the follow:
# sudo apachectl -k start
[warn] worker http://ip_maquina/ already used by another wor
Roy T. Fielding wrote:
> On Jul 14, 2009, at 10:02 AM, Nick Kew wrote:
>> That, on the other hand, stands. In the case of an HTTP/1.0
>> request, we'd be closing the connection to signal end-of-response.
>
> Not on a HEAD request.
But on the GET request with the deflate filter installed, we woul
On Jul 14, 2009, at 10:02 AM, Nick Kew wrote:
That, on the other hand, stands. In the case of an HTTP/1.0
request, we'd be closing the connection to signal end-of-response.
Not on a HEAD request.
Roy
Nick Kew wrote:
The content-length could've been set anyway - the simplest case being
a static file that's been "stat"ed. Have we definitely unset it?
D'oh. Of course we have.
Is this really an optimization? Sounds like correctness :) And do we
want
to also validate that Accept-Encoding
William A. Rowe, Jr. wrote:
Plüm, Rüdiger, VF-Group wrote:
+/*
+ * Optimization: If we are a HEAD request and bytes_sent is not zero
+ * it means that we have passed the content-length filter once and
+ * have more data to sent. This means that the content-lengt
On Jul 13, 2009, at 8:28 PM, William A. Rowe, Jr. wrote:
Just finished the last showstopper. I would be happy to advance this
to release / general availability vote with the next release, if we
can
determine just a few oddball issue resolutions. Jim and I have
already
gone ahead and moved
On Tue, Jul 14, 2009 at 11:54 AM, Jens Winter wrote:
> Hi,
>
> I wonder which rules are used to decide if a file is processed by PHP. For
> example x.php, x.php.bak and x.php.x~ are all processed, but x.php~ is not
> (at least by default). This could be an issue if you use vim or similar
> editors
Plüm, Rüdiger, VF-Group wrote:
>
> +/*
> + * Optimization: If we are a HEAD request and bytes_sent is not zero
> + * it means that we have passed the content-length filter once and
> + * have more data to sent. This means that the content-length filter
> +
> -Original Message-
> From: William A. Rowe, Jr.
> Sent: Montag, 13. Juli 2009 23:58
> To: dev@httpd.apache.org
> Subject: Re: mod_deflate DoS using HEAD
>
> Nick Kew wrote:
> > Eric Covener wrote:
> >
> >> /* For a 304 response, only change the headers */
> >> -if (
Hi,
I wonder which rules are used to decide if a file is processed by PHP.
For example x.php, x.php.bak and x.php.x~ are all processed, but x.php~
is not (at least by default). This could be an issue if you use vim or
similar editors to edit the config files of e.g. WordPress or MediaWiki
(co
On Jul 14, 2009, at 8:02 AM, Jorge Schrauwen wrote:
On Tue, Jul 14, 2009 at 2:28 AM, William A. Rowe,
Should we advertise the commands we have not implemented, or remove
them?
Yes, It's always useful to know for a more advance user.
+1 on keeping them.
Should we alert the user to the Se
On Tue, Jul 14, 2009 at 2:28 AM, William A. Rowe,
Jr. wrote:
> Just finished the last showstopper. I would be happy to advance this
> to release / general availability vote with the next release, if we can
> determine just a few oddball issue resolutions. Jim and I have already
> gone ahead and m
Plüm, Rüdiger, VF-Group wrote:
> Haven't thought this through but from a first glance it makes sense that
> the next provider can continue if the first one had a fatal error.
+1.
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Signature
> -Original Message-
> From: Eric Covener
> Sent: Montag, 13. Juli 2009 23:31
> To: dev@httpd.apache.org
> Subject: AuthBasicProvider failover and mod_authnz_ldap
>
> PR#47521 points out that when mod_authnz_ldap has some fatal LDAP
> connectivity error, it doesn't allow other AuthBas
16 matches
Mail list logo