ModPerl::Registry and Error Documents

Hi all,

after searching for a while without finding an answer to my question
I hope you can help me,

We're using mod_perl with ModPerl::Registry to have only a thin
layer between apache and our perl scripts. So far so good.
Now we want to produce error documents dynamically and thought
this could be achieved by simply producing a normal html document
and setting a status code > 400.

But it seems that the apache error handling jumps in as soon as
the code is seen and the html document is not delivered to
the client.

My question: Which is an easy and correct way to produce ErrorDocuments while
using ModPerl::Registry?

Best regards
Andreas

Re: ModPerl::Registry and Error Documents

On Tue 29 Sep 2009, Andreas Mock wrote:
> after searching for a while without finding an answer to my question
> I hope you can help me,
>
> We're using mod_perl with ModPerl::Registry to have only a thin
> layer between apache and our perl scripts. So far so good.
> Now we want to produce error documents dynamically and thought
> this could be achieved by simply producing a normal html document
> and setting a status code > 400.
>
> But it seems that the apache error handling jumps in as soon as
> the code is seen and the html document is not delivered to
> the client.
>
> My question: Which is an easy and correct way to produce
> ErrorDocuments while using ModPerl::Registry?

You have asked this question already 2 times before, on 17.09.09 12:13=20
and 17.09.09 11:15. The first time I have answered it.

If my answer is not satisfying could you be so kind and explain why?

If you want it to work the way you anticipate it should and it does not=20
then take a fresh copy from the SVN repository at=20
http://svn.eu.apache.org/repos/asf/perl/modperl/trunk and provide a=20
patch.

But please stop asking the same question again and again.

Glücklicherweise spreche ich die selbe Sprache wie Du. Also, Du hast=20
diese Frage schon 2 Mal gestellt. Beim ersten Mal habe ich geantwortet.

Wenn Dir meine Antwort nicht gefällt, könntest Du bitte erklären, was=
Du=20
daran auszusetzen hast?

Wenn modperl nicht so tut, wie Du denkst, es sollte, dann nimm einen=20
frischen Checkout von=20
http://svn.eu.apache.org/repos/asf/perl/modperl/trunk bau es nach=20
Deinem Geschmack um und stelle einen Patch zur Verfügung. Das ist der=20
beste/einzige Weg, die gewünschte Funktionalität in modperl zu kriegen.

Ich denke auch, daß es mit ParseHeaders und einer "Status: NNN" Zeile=20
tun sollte. Solange ich aber nicht direkt vor dem Problem stehe oder=20
nichts anderes zu tun habe, was nie passieren wird, werde ich das=20
Problem nicht angehen. So ähnlich denken wohl auch die anderen=20
Entwickler.

Bitte hör auf, ein und die selbe Frage immer wieder zu stellen.

Und übrigens, der Text in meiner Signatur ist ernst gemeint. Ich bin=20
käuflich.

Torsten

=2D-=20
Need professional mod_perl support?
Just hire me: torsten.foertsch@gmx.net

Re: ModPerl::Registry and Error Documents

> -----Ursprüngliche Nachricht-----
> Von: "Torsten Foertsch"
> Gesendet: 29.09.09 10:01:26
> An: modperl@perl.apache.org
> Betreff: Re: ModPerl::Registry and Error Documents

>=20
> You have asked this question already 2 times before, on 17.09.09 12:13=20
> and 17.09.09 11:15. The first time I have answered it.
>=20
> If my answer is not satisfying could you be so kind and explain why=3F

Hi Torsten, hi all others,

I have to apologize for sending the same question for many times.
I had problems with my mailer which let me think that my posts
never arrived at the mailing list. That was also the reason for
registring with another account, sending the question again.

Sorry for bothering.

Asking again was NOT a sign of being unsatisfied with an answer.
Sorry Torsten for giving you that feeling.

It was just me interpreting the outcome of an error the wrong way.
Shame on me.


>=20
> Und übrigens, der Text in meiner Signatur ist ernst gemeint. Ich bin=20
> käuflich.

Wer (im weitesten Sinne) nicht... ;-)

Best regards
Andreas