I've done a fair amount of searching and still can not find an answer to
this.
I'm writing a mod_perl2 handler and would like to output my own headers.
Specifically I'd like to output headers like this:
-
ICY 200 OK
icy-notice1: some info
icy-name: some info
icy-url:
I run a site with a few million MySQL requests a day, but I've run
into a strange problem which I'm trying to slove.
The server is running Apache 2.0.47, mod_perl2-1.99r09, DBI 1.38 and
DBD-mysql 2.1026 on a FreeBSD 4.8 machine.
About once or twice a day, I get a bunch of slow queries that
Hans wrote:
I've done a fair amount of searching and still can not find an answer to
this.
I'm writing a mod_perl2 handler and would like to output my own headers.
Specifically I'd like to output headers like this:
-
ICY 200 OK
icy-notice1: some info
icy-name: some
Hi,
This looks more like a MySQL problem than a specific MP2 issue. However here are a
couple of pointers.
All the queries below are updates on the same table this would indicate to me you may
be having a locking issue. What you need to do is locate the locking transaction it
may be as simple
The third beta of OpenInteract2 (1.99_03) has been released to CPAN
and Sourceforge. (Release 1.99_02 was skipped for consistency.) This
release includes:
* Many documentation updates, including a full package development
tutorial
* Actions can store messages to be passed from the controller
Hi,
I'm having trouble deciding what the best plan is for the arrangement of
the components of a new project that I'm starting.
The project is going to be written as a series of mod_perl handlers -
one for the main home page, and others for various sub-components.
Each handler is implemented
1.23
[ ENHANCEMENTS ]
- Lots of enhancements to the Apache.pm emulation when using the
CGIHandler module. Implemented by David Wheeler.
- The fact that autohandlers or dhandlers can be turned off by setting
autohandler_name or dhandler_name to has now been documented, and
we explicitly check
On Mon, 2003-09-08 at 11:51, Steve Hay wrote:
It also needs to have access to various static resources (images,
stylesheets, JavaScript libraries etc.).
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject/component2
Hi!
On Mon, Sep 08, 2003 at 04:51:55PM +0100, Steve Hay wrote:
The project is going to be written as a series of mod_perl handlers -
one for the main home page, and others for various sub-components.
Each handler is implemented by a separate module (all sub-classes of a
common base
assbackwards works. Thanks!
When I first read your response about a method called assbackwards I
thought it was sarcasm :)
understandable :)
actually, the assbackwards slot of the request record is there to indicate
that the incoming request used HTTP/0.9, which defines only GET and where no
Steve Hay [EMAIL PROTECTED] wrote
It also needs to have access to various static resources (images,
stylesheets, JavaScript libraries etc.).
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject/component2 [mp1]
...
On Mon, 2003-09-08 at 13:12, Geoffrey Young wrote:
actually, the assbackwards slot of the request record is there to indicate
that the incoming request used HTTP/0.9, which defines only GET and where no
headers are expected in the response.
Clearly this works, but wouldn't it be better to
Perrin Harkins wrote:
On Mon, 2003-09-08 at 13:12, Geoffrey Young wrote:
actually, the assbackwards slot of the request record is there to indicate
that the incoming request used HTTP/0.9, which defines only GET and where no
headers are expected in the response.
Clearly this works, but
On Mon, 2003-09-08 at 11:51, Steve Hay wrote:
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject/component2 [mp1]
...
/myproject/images [static]
/myproject/javascript [static]
/myproject/stylesheets [static]
btw, can you please explain what ICY is for me? the $r-assbackwards(1)
thing was specifically implemented in mod_perl 1.0 to support ICY, and I
used it in examples I give of this, but I always have to say that I have
no
idea what ICY is.
IceCast. The LINUX version of WinAmp's streaming MP3
Just curious ... what happens if I call 'die' in a mod_perl handler
(especially a CleanupHandler)? Does it actually kill the apache
child or does something catch the exception before that happens?
--
Ray Zimmerman / e-mail: [EMAIL PROTECTED] / 428-B Phillips Hall
Sr Research / phone:
Tim Edwards wrote:
I'm sending 3 cookies. The first one goes properly. The second two get
print to the screen. Same script run under normal perl works fine.
Suggestions?
Just a suggestion, but are you sure that you don't print out the
content-type header after sending the first cookie ? It
On Mon, 2003-09-08 at 16:10, Ray Zimmerman wrote:
Just curious ... what happens if I call 'die' in a mod_perl handler
(especially a CleanupHandler)? Does it actually kill the apache
child or does something catch the exception before that happens?
The latter. Your 'die' is caught by
Geoffrey Young wrote:
Perrin Harkins wrote:
On Mon, 2003-09-08 at 13:12, Geoffrey Young wrote:
actually, the assbackwards slot of the request record is there to
indicate
that the incoming request used HTTP/0.9, which defines only GET and
where no
headers are expected in the response.
Esteban Fernandez Stafford wrote:
Hello all,
I have a machine acting as a proxy using mod_perl-1.99_09 with apache
2.0.46. This proxy is supposed to filter all html content. So far I
have achieved most of my project's goals. But there is one issue I
can't get straight, this is when the proxy gets
Adam Kennedy wrote:
For those interested, I've been doing a general clean up of the code
( shrinking the code size down mainly ), prior to starting further work
on it.
Code available on request.
My intentions is to keep it as light as possible. While Apache::Fake
seems to be able to do a very
At 6:19 PM -0400 9/8/03, Perrin Harkins wrote:
On Mon, 2003-09-08 at 16:10, Ray Zimmerman wrote:
Just curious ... what happens if I call 'die' in a mod_perl handler
(especially a CleanupHandler)? Does it actually kill the apache
child or does something catch the exception before that happens?
Stas Wrote:
I believe it's not the problem Bart was talking about. You are most
likely talking about Apache-request failing, which is how it should be
if the GlobalRequest option is not set. Bart's problem was finding
the request method.
If you'll read carefully, you'll see that I'm talking
Philip M. Gollucci wrote:
Stas Wrote:
I believe it's not the problem Bart was talking about. You are most
likely talking about Apache-request failing, which is how it should be
if the GlobalRequest option is not set. Bart's problem was finding
the request method.
If you'll read carefully,
24 matches
Mail list logo
