rnier (tomcat):
On 22.07.2016 11:00, yhp...@orange.fr wrote:
Hello,
We have some handlers which were written by modperl for API endpoints.
yes developing a apache handler with modperl is so easy and quick.
but for better performance we also consider the C handler.
(one of the APIs has got 1,50
rl is powerful.
regards.
On 2016/7/22 17:53, André Warnier (tomcat) wrote:
On 22.07.2016 11:00, yhp...@orange.fr wrote:
Hello,
We have some handlers which were written by modperl for API endpoints.
yes developing a apache handler with modperl is so easy and quick.
but for better performance we
On 22.07.2016 11:00, yhp...@orange.fr wrote:
Hello,
We have some handlers which were written by modperl for API endpoints.
yes developing a apache handler with modperl is so easy and quick.
but for better performance we also consider the C handler.
(one of the APIs has got 1,500,000 accesses by
Hello,
We have some handlers which were written by modperl for API endpoints.
yes developing a apache handler with modperl is so easy and quick.
but for better performance we also consider the C handler.
(one of the APIs has got 1,500,000 accesses by unique clients)
Do you think if it's val
As you have eluded to, it is the request (not the server) which
can be configured as such. Possibly this would work for you:
PerlTransHandler +Local::Handlers->startup
PerlTransHandler +Local::Handlers->startup
package Local::Handlers;
# ...
sub startup {
my $r = ref($_[0])
I can set handlers directly from Apache config:
PerlResponseHandler code::A
PerlResponseHandler code::B
code A called only once and code B once too, only for specific Virtual Hosts.
I need to make same config from my startup perl script, I want to read
some own config data and then
>
> To do access control for static files while still using your mod_perl
> auth handler, take a look at mod_auth_tkt or perlbal.
>
Thanks!
> things.
It depends on the size of your httpd processes with mod_perl enabled.
If you have handlers that don't load a lot of third party modules, you
can get away with 10-20 meg mod_perl httpds. And a fair amount of
that memory will be shared.
On Sun, Mar 28, 2010 at 3:41 PM, Dan Axtell wrote:
> What I don't understand is what to do about static directories that want to
> use the handlers via Directory directive, or via a local .htdocs file. Does
> any such directory need to be forwarded to the dynamic server in order
>
> It would be more logical to do the authentication on the front-end
> server. Then, if the back-end server needs the result of the
> authentication, you could add an appropriate HTTP header (with the
> user-id and maybe more stuff) to the request, before proxying it to the
> back-end.
> The idea
Dan Axtell wrote:
Hi,
I wrote some mod_perl handlers for authentication and authorization, basically
to set cookies and check user roles. I use them for both static and dynamic
content from Perl scripts.
I'm looking into splitting Apache into two servers, one optimized for static
co
Hi,
I wrote some mod_perl handlers for authentication and authorization, basically
to set cookies and check user roles. I use them for both static and dynamic
content from Perl scripts.
I'm looking into splitting Apache into two servers, one optimized for static
content and acting
Iain Kennedy wrote:
Hi,
Is there a data structure that gets passed to each response handler in
the chain that the processed file can be stored in (like $f->ctx)?
Can the old mod_perl1 ->filter_input behaviour be done by manipulating
the input_filter or output_filter stacks?
Is what I'm trying
; Hi,
>
> I'm in the process of upgrading an application to mod_perl2. The
> application currently relies on chained content handlers. Each
> PerlResponseHandler in the chain uses the following mechanism to get
> (and then process) the requested file:
>
> $r->filter
Hi,
I'm in the process of upgrading an application to mod_perl2. The
application currently relies on chained content handlers. Each
PerlResponseHandler in the chain uses the following mechanism to get
(and then process) the requested file:
$r->filter_register;
my ($fh, $status) = $s
Hi,
I'm trying to figure out if anything ever happened with this bug where
internal redirects cause method handlers to get called as subs.
http://marc.info/?l=apache-modperl-dev&m=101261915419106&w=2
http://marc.info/?l=apache-modperl&m=106839932418976&w=2
The thread end
On Sun 02 Nov 2008, Puneet Lakhina wrote:
> One more question, is it possible for me to ensure that my module/or
> essenially mod_perl's processing of the URI translation happens
> before mod_rewrite or any other similar modules, and essentially
> mod_rewrite's rules work on the URI modified by me.
>> Then the documentation is wrong.
Yeah I ran it with PerlTransHandler. It works. So the documentation is
indeed misleading. Thanks for taking time to give such detailed
explanation.
One more question, is it possible for me to ensure that my module/or
essenially mod_perl's processing of the URI t
g but implemented that way
in apache, let's have a look at the ultimate docs. In
httpd-2.x.y/server/protocol.c you'll find the ap_read_request function.
It reads in a request, finds the virtual host that handles the request
and calls PostReadRequest handlers. It is a bit lengt
On Sun 02 Nov 2008, Puneet Lakhina wrote:
> > Input headers are found in $r->headers_in and are set even before
> > PerlPostReadRequest. So, have a close look at your code. If that
> > doesn't help try to create a test case as simple as you can and
> > post it to the list.
>
> Not as per this:
> ht
> Input headers are found in $r->headers_in and are set even before
> PerlPostReadRequest. So, have a close look at your code. If that
> doesn't help try to create a test case as simple as you can and post it
> to the list.
>
Not as per this:
http://perl.apache.org/docs/2.0/api/Apache2/RequestRec.h
On Sun 02 Nov 2008, Puneet Lakhina wrote:
> Initially I thought PerlTransHandler would be the right thing to use.
It is.
> But as it turns out, the headers arent populated until that phase.
Input headers are found in $r->headers_in and are set even before
PerlPostReadRequest. So, have a close l
Hi,
I am new to mod perl and apache. I am trying to write a URI
translation engine which needs to use the cookies set on the client.
Additionally I want mod_rewrite and other URI Translational hooks to
be invoked once my hook is done.
Initially I thought PerlTransHandler would be the right thing
Just the answer I was looking for. Thanks, Torsten
- Stephen
Torsten Foertsch wrote:
On Sat 02 Aug 2008, Stephen Howard wrote:
I'm issuing a lookup_uri request to launch a subrequest. I'm getting
a 404 on the subrequest when I get a 200 OK response when visiting
the same uri from a browse
On Sat 02 Aug 2008, Stephen Howard wrote:
> I'm issuing a lookup_uri request to launch a subrequest. I'm getting
> a 404 on the subrequest when I get a 200 OK response when visiting
> the same uri from a browser. My suspicion is that this uri, which
> uses a PerlInitHandler to transform the incom
I'm issuing a lookup_uri request to launch a subrequest. I'm getting a
404 on the subrequest when I get a 200 OK response when visiting the
same uri from a browser. My suspicion is that this uri, which uses a
PerlInitHandler to transform the incoming url, can't be found under the
subrequest b
It works !
Thanks a lot.
One additionnal question: does the hook ordering work (according to the
mod_perl documentation, it does not !) ?
Gaetan
2008/4/29, Philippe M. Chiasson <[EMAIL PROTECTED]>:
>
> titetluc titetluc wrote:
>
> > Hello,
> >
> > I am writing a new mod_perl Apache (mod_perl2) t
titetluc titetluc wrote:
Hello,
I am writing a new mod_perl Apache (mod_perl2) to manage session
tracking and SSO
This module defines a new Apache directive (MyNewDirective), which is
usable in a , block.
For example
Set-Handler perl-script
MyNewDirective a_test arg1 arg2
PerlR
Hello,
I am writing a new mod_perl Apache (mod_perl2) to manage session tracking
and SSO
This module defines a new Apache directive (MyNewDirective), which is usable
in a , block.
For example
Set-Handler perl-script
MyNewDirective a_test arg1 arg2
PerlResponseHandler ResponseHandler
On Sat, Mar 29, 2008 at 6:41 AM, André Warnier <[EMAIL PROTECTED]> wrote:
> Just for the rest of us : does anyone care to summarise what works and
> works not (inasfar as not necessarily documented and/or intuitive) ?
I think it's pretty well-documented:
http://perl.apache.org/docs/2.0/user/port
On Wed, Mar 26, 2008 at 9:47 AM, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
> > what about...
> >
> > PerlAccessHandler JetSet::Handler::AccessHandler
> >
> > sub AccessHandler {
> > my ($r) = @_;
> > }
>
> We seem to have solved the problem, but for the sake of conversation...
>
> Whe
On Wed, Mar 19, 2008 at 2:41 PM, John ORourke <[EMAIL PROTECTED]> wrote:
> The only down-side is that (AFAICR) it is creating a new object for each
> request
No, it's a class method. No object is created.
> PerlResponseHandler $My::Handlers::Persistent->response_hand
On Wed, Mar 19, 2008 at 2:22 PM, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
> In order to have many handlers in a file, I've put the following lines
> and other, similar lines in my virtual host configuration:
>
> PerlAccessHandler JetSet::Handler->AccessHandler
>
d
earlier."
(http://perl.apache.org/docs/2.0/user/handlers/http.html#PerlInitHandler)
Colin Wetherbee wrote:
� wrote:
Just for the rest of us : does anyone care to summarise what works
and works not (inasfar as not necessarily documented and/or
intuitive) ? And maybe what the original point of t
� wrote:
Just for the rest of us : does anyone care to summarise what works
and works not (inasfar as not necessarily documented and/or
intuitive) ? And maybe what the original point of this interesting
thread was ?
Sure, but I don't think we're finished quite yet. ;)
Colin
s that correct? :P
Also, I wonder if the difference is caused by the different ways we're
adding handlers? I specify mine in the virtual host configuration, and
it looks like you specify yours in startup.pl.
Colin
Hi.
Just for the rest of us : does anyone care to summarise what works and
works not (inasfar as not necessarily documented and/or intuitive) ?
And maybe what the original point of this interesting thread was ?
Thanks
André
Jonathan Vanasco wrote:
On Mar 28, 2008, at 3:11 PM, Colin Wether
On Mar 28, 2008, at 3:11 PM, Colin Wetherbee wrote:
Care to add one, just to see what happens? :)
You know you've been working too much on the Business Side when you
stop testing stuff like that automatically. sigh...
ok...
it works if i have
package MyApp;
sub handler {}
sub handler_
Jonathan Vanasco wrote:
On Mar 27, 2008, at 8:43 PM, Colin Wetherbee wrote:
Hm. Yep. ResponseHandler can interpret the ::ResponseHandler part as
being a function within Handler.pm, but that does *not* work for
InitHandler.
i have it set up using
PerlFixupHandler
PerlResponseHandler
On Mar 27, 2008, at 8:43 PM, Colin Wetherbee wrote:
Hm. Yep. ResponseHandler can interpret the ::ResponseHandler part
as being a function within Handler.pm, but that does *not* work for
InitHandler.
i have it set up using
PerlFixupHandler
PerlResponseHandler
PerlC
5 sites in production right now... and dating back to 03/04
with multiple specified handlers like that
I've never had that issue come up, nor have i planned for it. I could
see that happening though
Wow... again... I never thought of that.
Yep... here it is:
[Fri Mar 28 00:37:
right now... and dating back to
03/04 with multiple specified handlers like that
I've never had that issue come up, nor have i planned for it. I
could see that happening though
Wow... again... I never thought of that.
Jonathan Vanasco wrote:
On Mar 19, 2008, at 2:22 PM, Colin Wetherbee wrote:
PerlAccessHandler JetSet::Handler->AccessHandler
PerlResponseHandler JetSet::Handler->ResponseHandler
sub ResponseHandler
{
my (undef, $r) = @_;
# ...
}
what about...
PerlAccessHandler JetSet::Handler::AccessHand
On Mar 19, 2008, at 2:22 PM, Colin Wetherbee wrote:
PerlAccessHandler JetSet::Handler->AccessHandler
PerlResponseHandler JetSet::Handler->ResponseHandler
sub ResponseHandler
{
my (undef, $r) = @_;
# ...
}
what about...
PerlAccessHandler JetSet::Handler::AccessHandler
sub AccessHandler
André Warnier wrote:
PerlResponseHandler AM::TestStuff->handler
and
sub handler {
my ($self,$r) = @_;
$r->print('$self is a [' . ref($self) . '] and contains [' . $self .
"]\n");
[...]
and the result is
$self is a [] and contains [AM::TestStuff]
doesn't seem to be an object.
I get the
nseHandler JetSet::Handler->ResponseHandler
The only down-side is that (AFAICR) it is creating a new object for each
request - my handler is quite expensive to set up, so I have a
persistent object and use method handlers like this:
package My::Handlers;
$My::Handlers::Persistent=My::Handlers
John ORourke wrote:
The only down-side is that (AFAICR) it is creating a new object for each
request - my handler is quite expensive to set up, so I have a
persistent object and use method handlers like this:
Ah, that's quite neat. I might give that a shot.
Thanks for the suggestion.
Colin
t - my handler is quite expensive to set up, so I have a
persistent object and use method handlers like this:
package My::Handlers;
$My::Handlers::Persistent=My::Handlers->new();
sub response_handler { my ($self,$r)[EMAIL PROTECTED]; }
sub fixup_handler { my ($self,$r) = @_; }
a
André Warnier wrote:
In a similat setup, I successfuly use
my ($self, $r) = @_;
so, if the undef bothers you ..
:)
Do you actually use $self for anything?
Colin
In a similat setup, I successfuly use
my ($self, $r) = @_;
so, if the undef bothers you ..
;-)
Colin Wetherbee wrote:
Greetings.
In order to have many handlers in a file, I've put the following lines
and other, similar lines in my virtual host configuration:
PerlAccessHandler J
Greetings.
In order to have many handlers in a file, I've put the following lines
and other, similar lines in my virtual host configuration:
PerlAccessHandler JetSet::Handler->AccessHandler
PerlResponseHandler JetSet::Handler->ResponseHandler
Then, my handlers look like
Hello all,
I would like to use attributes (Attribute::Handlers) in a mod_perl module.
I defined my attribute:
use Attribute::Handlers;
sub Catch_error ATTR(CODE, BEGIN) { ... }
My module uses this attribute:
sub foo :Catch_error{
}
But this does not work.
I searched in the mod_perl mailing
Am Dienstag, 25. September 2007 schrieb Torsten Krah:
> Am Dienstag, 25. September 2007 schrieben Sie:
> > On 9/25/07, Torsten Krah <[EMAIL PROTECTED]> wrote:
> > > mod_jk registers the same way for Locations like mod_perl does.
> > > Can i register "2&quo
Am Dienstag, 25. September 2007 schrieben Sie:
> On 9/25/07, Torsten Krah <[EMAIL PROTECTED]> wrote:
> > mod_jk registers the same way for Locations like mod_perl does.
> > Can i register "2" handlers or how can i solve this problem?
> >
> > I want t
On 9/25/07, Torsten Krah <[EMAIL PROTECTED]> wrote:
> mod_jk registers the same way for Locations like mod_perl does.
> Can i register "2" handlers or how can i solve this problem?
>
> I want to filter the output from mod_jk (SetHandler jakarte-servlet) - but i
ations like mod_perl does.
Can i register "2" handlers or how can i solve this problem?
I want to filter the output from mod_jk (SetHandler jakarte-servlet) - but i
cannot set both in apache configuration file?
Is there a way to get this working or should i stay with mod_proxy_ajp because
Torsten Foertsch wrote:
On Wednesday 20 June 2007 09:45, Cyril SCETBON wrote:
Are we able to disable the chunk transfer ? To send all in one shot ?
Add a Content-Length output header and avoid output filters that can change
the content length.
Great. It works :-) when using $r->ser_content
Torsten Foertsch wrote:
On Wednesday 20 June 2007 09:45, Cyril SCETBON wrote:
Are we able to disable the chunk transfer ? To send all in one shot ?
Add a Content-Length output header and avoid output filters that can change
the content length.
Great. It works :-) when using $r->ser_content
On Wednesday 20 June 2007 09:45, Cyril SCETBON wrote:
> Are we able to disable the chunk transfer ? To send all in one shot ?
Add a Content-Length output header and avoid output filters that can change
the content length.
Or use HTTP/1.0
Torsten
pgpytV5g1jL48.pgp
Description: PGP signature
Are we able to disable the chunk transfer ? To send all in one shot ?
Geoffrey Young wrote:
Cyril SCETBON wrote:
Hi people,
I've got some problem with both cgi and modperl.
when I post something to /perl/test.pl which just print header and a
string I got some strange numbers. The post is do
Cyril SCETBON wrote:
> Hi people,
>
> I've got some problem with both cgi and modperl.
> when I post something to /perl/test.pl which just print header and a
> string I got some strange numbers. The post is done with a php script.
>
> test.pl :
>
> use strict;
> use CGI qw/:standard/;
>
> pri
Hi people,
I've got some problem with both cgi and modperl.
when I post something to /perl/test.pl which just print header and a
string I got some strange numbers. The post is done with a php script.
test.pl :
use strict;
use CGI qw/:standard/;
print header;
print("\ncoucou\n");
and below i
On Jan 15, 2007, at 3:04 PM, John ORourke wrote:
The thought process I've gone through corroborates this - at the
most complex point I was looking at specifying a caching policy for
each table - eg. (in a shop website) product info except stock
levels can be cached for a day, static pages
Perrin Harkins wrote:
On Mon, 2007-01-15 at 13:02 -0600, Frank Wiles wrote:
Not being a MySQL guy this could be fixed now, but last I heard
MySQL tossed it's cache anytime the table was updated. Not very
efficient IMHO.
Yes, modifying data in a table invalidates the cache fo
On Mon, 2007-01-15 at 13:02 -0600, Frank Wiles wrote:
>Not being a MySQL guy this could be fixed now, but last I heard
>MySQL tossed it's cache anytime the table was updated. Not very
>efficient IMHO.
Yes, modifying data in a table invalidates the cache for that table.
There's really
On Mon, 15 Jan 2007 11:38:34 -0500
Perrin Harkins <[EMAIL PROTECTED]> wrote:
> > - if MySQL's cache is very efficient, should I bother caching in
> > my own code?
Not being a MySQL guy this could be fixed now, but last I heard
MySQL tossed it's cache anytime the table was updated. Not ver
On Mon, 2007-01-15 at 15:54 +, John ORourke wrote:
> - MySQL caches compiled statements, so why should I bother using
> prepare/execute?
Do you mean "Why should I bother using prepare_cached?" The reason for
that is the additional overhead of object creation that it avoids on the
database c
Hi folks, please humour me with this slightly OT RFC...
So I've re-invented the wheel (or MVC framework) and need to make it
efficient. A high-traffic site is using the system and is causing me
some grief...
Some questions have come up re efficient caching:
- MySQL caches compiled statement
Sylvain Perrot wrote:
> Hi,
>
> This is working !!!
> Good point... But how to handle the authentication as I wanted (no http
> authentication but my own authentication module ...)
you can always use your own authentication module, but you need to be
sure to follow the proper steps. what those a
: Modperl Mailing List
Subject: Re: [mp2] Perl Auth Handlers and mod_proxy : losing querystring
on remote server (BUG?)
>
>AuthType Basic
>AuthName "Test Authentication"
>AuthUserFile /www/xperience.ch/conf/.htpasswd
>require valid-user
>
next test
Geoffrey Young wrote:
>>
>> AuthType Basic
>> AuthName "Test Authentication"
>> AuthUserFile /www/xperience.ch/conf/.htpasswd
>> require valid-user
>>
>
>
> next test -
I won't be able to do any more work tonight, so if this doesn't work
here's what I'd suggest...
are you running any
>
>AuthType Basic
>AuthName "Test Authentication"
>AuthUserFile /www/xperience.ch/conf/.htpasswd
>require valid-user
>
next test - keep all that the same but substitute
PerlAuthenHandler My::Authen
for
AuthUserFile /www/xperience.ch/conf/.htpasswd
and use this handler:
the querystring to the remote server !!!
Sylvain
-Original Message-
From: Perrin Harkins [mailto:[EMAIL PROTECTED]
Sent: mercredi, 10. janvier 2007 01:10
To: Sylvain Perrot
Cc: Modperl Mailing List
Subject: Re: [mp2] Perl Auth Handlers and mod_proxy : losing querystring
onremote server
ronment to
test if he got the same problem, it would be great !
Best regards
Sylvain
-Original Message-
From: Geoffrey Young [mailto:[EMAIL PROTECTED]
Sent: mercredi, 10. janvier 2007 01:16
To: Perrin Harkins
Cc: Sylvain Perrot; Modperl Mailing List
Subject: Re: [mp2] Perl Auth Ha
Perrin Harkins wrote:
> Does it help any if you use ProxyMatch instead of LocationMatch?
also, try substituting your PerlAuthenHandler for normal .htpasswd-style
authentication at the same place - mod_perl doesn't do much to interact
with the request record, which is where the query string is stor
ntext:
http://www.nabble.com/Perl-handlers-PerlAuthenHandler-tf2949783.html#a8249688
Sent from the mod_perl - General mailing list archive at Nabble.com.
Does it help any if you use ProxyMatch instead of LocationMatch?
- Perrin
>
Hi,
After 2 days trying to resolve my problem, I am close to think about a
bug in mod_perl used with mod_proxy.
let summarize my problem in case someone could help me :
CLIENT --> Reverse-Proxy ---> Application Servers
Reverse-Proxy is : Linux, Apache 2.0.59, mod_perl 2.0.3
Applicat
Ahh, I see. Great tip. Thanks alot.
Jordan
On 10/27/06, John ORourke <[EMAIL PROTECTED]> wrote:
Jordan McLain wrote:
> just noticed... in the actual code 'handler' is prototyped with ($$)
>
>
>> sub handler {
>> my ($class, $r) = @_;
>>
>> my $self = ... # something hashref-ish
>
>> I wil
Jordan McLain wrote:
just noticed... in the actual code 'handler' is prototyped with ($$)
sub handler {
my ($class, $r) = @_;
my $self = ... # something hashref-ish
I will end up writing another "new()" for use when not called directly
from apache. Is this bad style, since the method
just noticed... in the actual code 'handler' is prototyped with ($$)
On 10/26/06, Jordan McLain <[EMAIL PROTECTED]> wrote:
Hello,
This is more of a style and usage question. Sorry for the stupid question.
I am rewriting one of my apps to be more OO so that I can abstract
its' functionality o
Hello,
This is more of a style and usage question. Sorry for the stupid question.
I am rewriting one of my apps to be more OO so that I can abstract
its' functionality out to another handler potentially. I end up doing
something like this...
sub handler {
my ($class, $r) = @_;
my $self = ...
John ORourke wrote:
I would strongly recommend using one of the well used frameworks. You
can find more info and tutorials from the links on this page:
http://perl.apache.org/products/app-server.html
How come Catalyst is not on that page? Someone might as well add it.
Enno
On Aug 1, 2006, at 10:45 AM, John ORourke wrote:
Excellent, I'd never heard of that. I only found out about
Class::DBI yesterday too - next thing you'll be telling me there's
a guide that picks out the most useful CPAN modules to stop people
reinventing the wheel!
Personally, I disliked
John ORourke wrote:
>
> Michael Peters wrote:
>
>> John ORourke wrote:
>>
>>
>>> You could even do something really clever and make it map URI onto
>>> module - eg. so /debitor/contract/create calls
>>> Debitor::Contract->create(), but that wouldn't be very secure!
>>>
>>
>> You could use
Michael Peters wrote:
John ORourke wrote:
You could even do something really clever and make it map URI onto
module - eg. so /debitor/contract/create calls
Debitor::Contract->create(), but that wouldn't be very secure!
You could use something like Apache::Dispatch to achieve this or
John ORourke wrote:
> You could even do something really clever and make it map URI onto
> module - eg. so /debitor/contract/create calls
> Debitor::Contract->create(), but that wouldn't be very secure!
You could use something like Apache::Dispatch to achieve this or
CGI::Application::Dispatch
> Frank Maas wrote:
>
>> On Tue, Aug 01, 2006 at 07:33:51AM +0100, John ORourke wrote:
>>
>>
>>> You could even do something really clever and make it map URI onto
>>> module - eg. so /debitor/contract/create calls
>>> Debitor::Contract->create(), but that wouldn't be very secure!
>
> As descri
Vladimir S. Tikhonjuk wrote:
John ORourke пишет:
Vladimir S. Tikhonjuk wrote:
O.K. Thanks for answer :)
I want to write rather big project. How I have to construct it: I mean,
should I make a lot of handlers, like, /debitor, /debitor/documents,
/debitor/documents/contracts Or
Frank Maas wrote:
On Tue, Aug 01, 2006 at 07:33:51AM +0100, John ORourke wrote:
You could even do something really clever and make it map URI onto
module - eg. so /debitor/contract/create calls
Debitor::Contract->create(), but that wouldn't be very secure!
Why would that be not very
On Tue, Aug 01, 2006 at 07:33:51AM +0100, John ORourke wrote:
>
> You could even do something really clever and make it map URI onto
> module - eg. so /debitor/contract/create calls
> Debitor::Contract->create(), but that wouldn't be very secure!
>
Why would that be not very secure? Could you g
John ORourke пишет:
> Vladimir S. Tikhonjuk wrote:
>
>>
>> O.K. Thanks for answer :)
>> I want to write rather big project. How I have to construct it: I mean,
>> should I make a lot of handlers, like, /debitor, /debitor/documents,
>> /debitor/documents/contra
Vladimir S. Tikhonjuk wrote:
O.K. Thanks for answer :)
I want to write rather big project. How I have to construct it: I mean,
should I make a lot of handlers, like, /debitor, /debitor/documents,
/debitor/documents/contracts Or, create *.pl scripts. Or may be
there is another theory
one handler will run - not both. But otherwise yes.
>
> Basically for each section of Apache, one thing wins. Mostly you can
> think of sections as Authentication, Authorization, and Handler (there
> are others of course, especially filters, fixup handlers and more -
> but the first
of course, especially filters, fixup handlers and
more - but the first three are the most common).
So if you have:
Auth...
Handler Debitor::Documents
Handler Debitor
Then the Auth handler will not be effected by the other entries
Scott Penrose пишет:
>
> On 01/08/2006, at 15:30, Vladimir S. Tikhonjuk wrote:
>
>> Hi everyone!
>>
>> I have Authentication handler, which I set like:
>>
>>
>> PerlAuthenHandler Promtelecom::Authentication
>> AuthType Basic
>> AuthName "Promtelecom Network"
>> Require valid-user
>>
>>
>> Alseo
On 01/08/2006, at 15:30, Vladimir S. Tikhonjuk wrote:
Hi everyone!
I have Authentication handler, which I set like:
PerlAuthenHandler Promtelecom::Authentication
AuthType Basic
AuthName "Promtelecom Network"
Require valid-user
Alseo I have 2 simple PerlHandler's
Hi everyone!
I have Authentication handler, which I set like:
PerlAuthenHandler Promtelecom::Authentication
AuthType Basic
AuthName "Promtelecom Network"
Require valid-user
Alseo I have 2 simple PerlHandler's: Debitor and DebitorDocuments, which
set like:
PerlM
On Jul 28, 2006, at 10:12 AM, Michael Peters wrote:
>> a lot of stuff i agree with here, and then
The easiest solution is to just run 2 apaches. Configure pre-prod
for a
different port. You can even run them from the same apache binary,
just give
them different configs to start off.
i'll
Matthew wrote:
> Hey gang, happy friday!
>
> We have two trees for our web app:
>
>Prod -> /pages/sc2/roomlogin?
> PreProd -> /pages/sctest/roomlogin?
>
> httpd.conf:
>
> Location /pages/sc2/roomlogin -> /path/pages/sctest/omno/prod.pm
> Location /pages/sctest/roomlogin -> /path/pages
1 - 100 of 221 matches
Mail list logo
