(from https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75194)
Hi,
The technique presented in
http://perl.apache.org/docs/2.0/devel/porting/porting.html#Requiring_a_specific_mod_perl_version_
doesn't work with mod_perl 1.99 in the server config files. The perl
code sample in the document
On Tue, 5 Nov 2002 at 22:52, Chris Shiflett opined:
[snip]
CS:The W3C's stance on refresh is the same for the header as well as the
CS:meta tag: they did not originally intend for it to be used to specify a
CS:*different* URL as a rudimentary method of redirection. They meant it to
CS:be used
The uploaded file
Apache-NavBarDD-0.71.tar.gz
has entered CPAN as
file: $CPAN/authors/id/L/LO/LOURIDAS/Apache-NavBarDD-0.71.tar.gz
size: 7324 bytes
md5: ba426f5c30a19915572d28b888a6e57d
Description
---
The Apache::NavBarDD package provides a dynamic navigation bar along the
I just wanted to mention that the meta tag as well as its http-equiv
attribute are both official parts of the HTML standard and have been for
quite some time.
Yes and no.
HTML 4.0 has a section on META and http-requiv. In it, it mentions that
Some user agents support the use of META to
--- Perrin Harkins [EMAIL PROTECTED] wrote:
I might be overzealous about this, but I dislike seeing HTTP-EQUIV
meta
tags used when actual HTTP headers are available to do the same
thing.
It's fine if there's a reason for it, but usually people do it
because
they don't realize they can
hi all...
we have received a few requests for an electronic version of the
mod_perl Developer's Cookbook over the past few months, which we have
thus far been unable to satisfy. yesterday I noticed that it has
finally shown up on Safari:
http://safari.informit.com/0672322404
so, for
Greetings.
[...]
[snip]
CS:The W3C's stance on refresh is the same for the header as
well as the
CS:meta tag: they did not originally intend for it to be used
to specify a
CS:*different* URL as a rudimentary method of redirection.
[...]
i was bitten by this assumption recently. case
hi all,
i'm actually working on a system where a user can create domains /
subdomains throug a webinterface and doesn't have to interact with the
httpd.conf.
For this I use a unique virtualhost which intercept all client request
no matter which vh is requested. After a handler treat the
List,
Tired of having 10 modules all with near identical handler methods I
decided to put the handler method into a superclass and be done with
maintaining the same code 10 times. I first tried this a couple of weeks ago
and it failed to work, because at the time I couldn't find the reference
On Wed, Nov 06, 2002 at 11:52:13AM -0500, Vivek Khera wrote:
What they should have done is what is done now with TLS in SMTP. You
connect to the same port, but issue a STARTTLS command to switch
over to secured mode. With this type of scheme, the header info with
the desired host could be in
I should add that this segv only happens when using push_handlers like
below. If I put Control::Super::Sub-handler inside a Location tag in
httpd.conf then it is fine.
Ric
- Original Message -
From: Richard Clarke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 06, 2002
Geoffrey Young wrote:
keep in mind that neither book mentions the use of subroutine
attributes, which is allowed in 1.3 but the only way in 2.0
sub handler : method {
...
}
I am 99% sure that Attribute handlers wont work in 1.3 because
Attribute::Handlers use CHECK{} blocks to set up the
Mathieu Jondet [EMAIL PROTECTED] wrote:
hi all,
i'm actually working on a system where a user can create domains /
subdomains throug a webinterface and doesn't have to interact with the
httpd.conf.
For this I use a unique virtualhost which intercept all client request
no matter which vh is
Michael Schout wrote:
Geoffrey Young wrote:
keep in mind that neither book mentions the use of subroutine
attributes, which is allowed in 1.3 but the only way in 2.0
sub handler : method {
...
}
I am 99% sure that Attribute handlers wont work in 1.3 because
Attribute::Handlers use
Now I feel stupid. $sub-handler was supposed to be $sub-handler.
That's what you get for being impatient.
Ric
- Original Message -
From: Richard Clarke [EMAIL PROTECTED]
To: Richard Clarke [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, November 06, 2002 4:08 PM
Subject: Re: OO
Richard Clarke [EMAIL PROTECTED] wrote:
Now I feel stupid. $sub-handler was supposed to be $sub-handler.
That's what you get for being impatient.
or perhaps `sub { $sub - handler(@_) }' -- if quoting works,
great, but I would fear that $sub-handler would stringify before
push_handlers got
I just wanted to mention that the meta tag as well as its http-equiv
attribute are both official parts of the HTML standard and have been
for quite some time.
Yes and no.
Well, I disagree with the no. I will explain it again below.
HTML 4.0 has a section on META and
Richard Clarke wrote:
List,
Tired of having 10 modules all with near identical handler methods I
decided to put the handler method into a superclass and be done with
maintaining the same code 10 times. I first tried this a couple of weeks ago
and it failed to work, because at the time I
- Original Message -
From: Vivek Khera [EMAIL PROTECTED]
Newsgroups: ml.apache.modperl
To: [EMAIL PROTECTED]
Sent: Wednesday, November 06, 2002 6:52 PM
Subject: Re: sending ssl certificate according to virtual host
MJ == Mathieu Jondet [EMAIL PROTECTED] writes:
MJ Depending on the
MJ == Mathieu Jondet [EMAIL PROTECTED] writes:
MJ Depending on the vh requested I set the SSLCertificateFile and
MJ SSLCertificateKeyFile which will point to the correct ssl files for the
MJ requested vh.
You can't do this with name-based vhosts. To present the proper SSL
certificate, you have
Hey guys,
You may remember me from such messages as I can't get mod_perl to compile on Irix64
systems!. Well now I've got a whole new problem that I need your expertise on.
I'm running Apache 1.3x and mod_perl 1.2x on a Linux system. However, whenever I go
to a page that should be handled by
Hi All,
I have the following scenario:
* A Perl Handler i have written does a bit of work and
outputs HTML
* The HTML it outputs contains HTML like:
!--#include virtual=/includes/misc/topnav.html --
I need this to be further parsed by Apache's Server Parsing
Process.
Seems somewhat similar to a bug I've reported 10 months ago.
You might want to try to run the minimal testcase enclosed in the
forwarded mail.
Phil.
---BeginMessage---
I've found that mod_perl can get confused when dealing with method
calls during a redirect_internal phase:
1. page /1 uses
On the use of META REFRESH tags, Chris wrote:
It is also the only option for the pause, then redirect behavior the
original poster desired that I can think of.
I also seem to recall reading in the HTTP spec (and in Lincoln's CGI.pm code)
that the use of a Redirect header in response to a POST
[EMAIL PROTECTED] wrote:
Also, NPH is only implemented in the NS browsers, and was a way for a webserver
to send multiple documents inline down to a browser, and was an ancient way
to write status pages and such that automagically refreshed themselves.
No, that's server push you're thinking
Hello Simran,
At 00:50 07.11.2002, simran wrote:
I have the following scenario:
* A Perl Handler i have written does a bit of work and
outputs HTML
* The HTML it outputs contains HTML like:
!--#include virtual=/includes/misc/topnav.html --
I need this to be further parsed
mod_perl VERSION: 1.25
Apache version: 1.3.26
Apache MMN: 19990320
make[1]: Entering directory
`/Andrews/tcbsrc/apache/mod_perl/backport/libapache-mod-perl-1.25'
make[2]: Entering directory
`/Andrews/tcbsrc/apache/mod_perl/backport/libapache-mod-perl-1.25/Apache'
make[2]: Leaving directory
27 matches
Mail list logo
