Hi everybody,
I'm designing an Web interface to edit configuration data stored in an XML
file.
To ensure data integrity, I have to avoid multiple users accessing URLs
that allow config modification I.E. file reading/writing.
Let say these URLs are located under location '/admin/config/'
I
Hi List,
New to mod_perl, but have a specific project in
mind, that will immerse me in it.
Wondering if someone could comment on both the
possibility of, and the wisdom of, pulling server configs dynamically from a
database WITHOUT requiring server restart.
Prime example: you've added a
A new version (1.40) of OpenInteract has been released to CPAN.
OpenInteract is an extensible web application server built on
Apache, mod_perl, the Template Toolkit and SPOPS object persistence.
OpenInteract now runs on Oracle -- with one minor caveat: sessions. Many
thanks to Ben Avery [EMAIL
I would have sent both to the client. The sequence would be *the* id and
is guaranteed to be uinique by the database (or whatever else is around
that does this reliably). The idea is that by combining the random secret
with the ID and sending the digest with that the ID number can't just be
[EMAIL PROTECTED] wrote:
I would have sent both to the client. The sequence would be *the* id and
is guaranteed to be uinique by the database (or whatever else is around
that does this reliably). The idea is that by combining the random secret
with the ID and sending the digest with that the
I ran into this problem during mod_perl development, and I'm posting it to
this list hoping that other mod_perl developers have dealt with the same
thing and have good solutions :)
I've found that strings collected while processing XML using XML::Parser do
not play nice with the HTML::Entities
[EMAIL PROTECTED] wrote:
digest source might be able to locate the bits just by trying a lot of
them. I would expire them after a while just to prevent that from
happening by stating that if there is a 15 minute session, new random bits
are generated each five minutes.
I missed the start of
The output from your example looks like UTF-8 data (Atilde; is a
commonly seen UTF-8 escape sequence). XML::Parser converts all
incoming text into UTF-8. You will need to convert it back to
iso-8859-1.
My favorite is Text::Iconv
use Text::Iconv;
$utf8tolatin1 =
Folks,
A pol of gee's in advance - this is probably an inane question for ye
olde mod_perl gods but I'll ask it anyway to see if I get struck by the
lightning of enlightenment!
All the e dot gee's that I can find, perldoc and guide pages show
sessions being used with a tied old hash interface -
John Siracusa wrote:
I ran into this problem during mod_perl development, and I'm posting it to
this list hoping that other mod_perl developers have dealt with the same
thing and have good solutions :)
I did ;-)
I've found that strings collected while processing XML using XML::Parser do
On 5/7/02 10:58 AM, Paul Lindner wrote:
The output from your example looks like UTF-8 data (Atilde; is a
commonly seen UTF-8 escape sequence). XML::Parser converts all
incoming text into UTF-8. You will need to convert it back to
iso-8859-1.
My favorite is Text::Iconv
use
On 5/7/02 11:06 AM, Rafael Garcia-Suarez wrote:
The workaround I used is to write the handler like this :
sub xml_char
{
my ($expat) = _;
$buffer .= $expat-original_string;
}
Reading the original string, no need to convert UTF-8 back to iso-8859-1.
Doh! I dunno why I didn't think
John Siracusa [EMAIL PROTECTED] writes:
On 5/7/02 10:58 AM, Paul Lindner wrote:
The output from your example looks like UTF-8 data (Atilde; is a
commonly seen UTF-8 escape sequence). XML::Parser converts all
incoming text into UTF-8. You will need to convert it back to
iso-8859-1.
Greetings.
Compiling and running the snapshots for BOTH apache and modperl (May 6th
snapshots)
on windowsNT sp6, I observe the following:
i) the tests punt on conftree.t (it goes on forever)
ii) installing and testing in a registry situation the request succeeds on
the first
invocation, but
On 5/7/02 11:25 AM, Gisle Aas wrote:
John Siracusa [EMAIL PROTECTED] writes:
On 5/7/02 10:58 AM, Paul Lindner wrote:
The output from your example looks like UTF-8 data (Atilde; is a
commonly seen UTF-8 escape sequence). XML::Parser converts all
incoming text into UTF-8. You will need to
(Anyone else, is there a module that already does this?)
That misses two things: random data is not unique and random data is
scarce.
The thread started where someone else wanted a cheap way to generate
difficult to guess and unique session ids. It went on around how using a
random function
On Tue, May 07, 2002 at 11:13:43AM -0400, John Siracusa wrote:
On 5/7/02 10:58 AM, Paul Lindner wrote:
The output from your example looks like UTF-8 data (Atilde; is a
commonly seen UTF-8 escape sequence). XML::Parser converts all
incoming text into UTF-8. You will need to convert it
I am writing a web application that uses Apache modules and core classes
in a MVC style. AFAICT using $r-log-debug() is the standard way to
print debug messages in Apache modules, but which would be the right way
to print debug messages in the core classes provided both types of
modules are
Hello,
Thanks for the suggestion, but it doesn't seem to make any difference.
I tried setting:
ProxyIOBufferSize 32768
ProxyReceiveBufferSize 32768
in my httpd.conf, and it is still calling my handler several times per
request...
I put in:
warn Size: . length($buffer) . \n;
in my while
Folks,
How do I get to log my mod_perl handler Perl errors to the browser
instead of into the Apache logs?
TIA
Jeff
Jeff wrote:
Folks,
How do I get to log my mod_perl handler Perl errors to the browser
instead of into the Apache logs?
see recipes 4.5 and (the more interestingly but less robust) 16.6 in the cookbook
the code for each is here
F.Xavier Noria wrote:
I am writing a web application that uses Apache modules and core classes
in a MVC style. AFAICT using $r-log-debug() is the standard way to
print debug messages in Apache modules, but which would be the right way
to print debug messages in the core classes provided both
22 matches
Mail list logo
