On Mon, Nov 15, 2010 at 3:56 AM, Matus UHLAR - fantomas
wrote:
>> >> On Thu, October 28, 2010 16:24, Tom Evans wrote:
>> >> > Why do you care what the status code is? (or rather, why do you want
>> >> > to return OK when an error occurs?)
>> >
>> > On 28.10.10 16:48, Joost de Heer wrote:
>> >> To
> >> On Thu, October 28, 2010 16:24, Tom Evans wrote:
> >> > Why do you care what the status code is? (or rather, why do you want
> >> > to return OK when an error occurs?)
> >
> > On 28.10.10 16:48, Joost de Heer wrote:
> >> To work around the "Display userfriendly error messages" bug^Wfeature?
>
On Tue, Nov 9, 2010 at 2:17 AM, Matus UHLAR - fantomas
wrote:
>> On Thu, October 28, 2010 16:24, Tom Evans wrote:
>> > Why do you care what the status code is? (or rather, why do you want
>> > to return OK when an error occurs?)
>
> On 28.10.10 16:48, Joost de Heer wrote:
>> To work around the "Di
> On Thu, October 28, 2010 16:24, Tom Evans wrote:
> > Why do you care what the status code is? (or rather, why do you want
> > to return OK when an error occurs?)
On 28.10.10 16:48, Joost de Heer wrote:
> To work around the "Display userfriendly error messages" bug^Wfeature?
Is there any need fo
On Fri, Oct 29, 2010 at 3:21 AM, Green Wang wrote:
> maybe you can use a script like php or what
> and set the ErrorDocument to this script
> then use header() function to set the response status code
>
IS there an example I can use? Or is there a better way of handling it?
> On 10/28/2010 10:24
On Thu, Oct 28, 2010 at 4:41 PM, William A. Rowe Jr.
wrote:
> On 10/28/2010 10:17 AM, Tom Evans wrote:
>> That has well known solutions doesn't it? Pad your page to more than
>> 512 bytes, and Robert is the brother of your mother.
>
> I don't know that 512 will do the trick in all cases.
>
> At on
maybe you can use a script like php or what
and set the ErrorDocument to this script
then use header() function to set the response status code
On 10/28/2010 10:24 PM, Tom Evans wrote:
You want it to fail and return 200? Seems counter-intuitive...
-
On 10/28/2010 10:17 AM, Tom Evans wrote:
> That has well known solutions doesn't it? Pad your page to more than
> 512 bytes, and Robert is the brother of your mother.
I don't know that 512 will do the trick in all cases.
At one point IE had me convinced that if the size of its message was longer
That has well known solutions doesn't it? Pad your page to more than
512 bytes, and Robert is the brother of your mother.
Cheers
Tom
On Thu, Oct 28, 2010 at 3:48 PM, Joost de Heer wrote:
> On Thu, October 28, 2010 16:24, Tom Evans wrote:
>
>> Why do you care what the status code is? (or rather,
On Thu, October 28, 2010 16:24, Tom Evans wrote:
> Why do you care what the status code is? (or rather, why do you want
> to return OK when an error occurs?)
To work around the "Display userfriendly error messages" bug^Wfeature?
Joost
On Thu, Oct 28, 2010 at 12:54 AM, Mohit Anchlia wrote:
> It looks like ErrorDocument changes the behaviour globally. What I
> need to do is return Http code 200 with customized message which
> clients can parse and display cleanly on the browser.
>
You want it to fail and return 200? Seems counte
It looks like ErrorDocument changes the behaviour globally. What I
need to do is return Http code 200 with customized message which
clients can parse and display cleanly on the browser.
On Wed, Oct 27, 2010 at 12:36 PM, Nick Kew wrote:
> On Wed, 27 Oct 2010 12:28:47 -0700
> Mohit Anchlia wrote:
On Wed, 27 Oct 2010 12:28:47 -0700
Mohit Anchlia wrote:
> Can someone suggest what would be the best options?
>
ErrorDocument
--
Nick Kew
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://
Apache 2.2
Requirement I am working on is to block the request body if it is
greatar than certain size. I can do this easily with LimitRequestBody
directive in virtual hosts but the problem comes when I want to send
customized message to the user instead of returning non 200 http code.
Can someon
14 matches
Mail list logo
