Re: mod_accel reverse proxying?
On Sat, 29 Dec 2001, Jeremy Howard wrote: > Philip Mak wrote: > > On Fri, 28 Dec 2001, Igor Sysoev wrote: > > > I think it should have reverse syntax: > > > > > > AccelReverse http://127.0.0.1:8001/ / > > > > > > Or not ? Of course it complicates porting from mod_proxy to mod_accel > > > but I think it's clearer then ProxyPassReverse syntax. > > > > I don't think either order is more clearer than the other, but since > > ProxyPassReverse has it like / http://127.0.0.1:8001/, my personal opinion > > is that AccelPassReverse should have it in the same order too to avoid > > confusion. > > > On the other hand, I find mod_proxy's syntax weird and support Igor's > proposal. Still, either one would be very handy! RewriteRule ^/$ http://backend/$1 AccelReverse / http://backend/ Today there will be mod_accel-1.0.10 and mod_deflate-1.0.10 tarballs. I'll post message. Igor Sysoev
Re: mod_deflate warning
On Sat, 29 Dec 2001, Jeremy Howard wrote: > I posted a couple of weeks ago about how well the mod_deflate/mod_accel > combination works on a front-end HTTP accelerator. I've just discovered a > problem that I thought I'd mention here for anyone who's trying this out. > > It appears that Mozilla-based browsers fail when using gzip encoding with > POST requests. I've added > DeflateDisableRange "MSIE 4." "Mozilla" > to my httpd.conf as a workaround for this bug. The bug appears > intermittently, and I haven't yet worked out exactly how to replicate it. > However, it's been reported by many of my users and I have experienced it > myself, so I'd suggest being wary of this combination. First, "DeflateDisableRange" doesn't disable gzipping - it disables partial responses (byte-range) if this request can be gzipped. If you want to disable gzipping for some browser you need to set enviroment variable: BrowserMatch "Gecko" no_gzip Second, don't use "Mozilla" string - this string is in all Netscape 1-6, and MSIE 1-6. Use "Gecko" instead - all Mozilla-derived browsers has this string. And third - can you send me all bug reports with Mozilla ? Igor Sysoev
Re: [OT] Re: XML::LibXML
try perldoc XML::LibXML i got this perl module working fine http://drfrog.fdns.net/x3d/ Per Einar wrote: > At 16:58 28/12/01, Fred wrote: > >> I know (guess?) my answer in somwhere linked with Dynaloader. >> But I do not find the link between XML::LibXML and libxml2. Do not >> man have >> to specify it somewhere? Where is the link between C libs and Perl? >> How come can calls to undefined methods like $self->_parse_file() (in >> method >> XML::LibXML->parse_file()) can be found? Where is the inheritance >> defined? >> >> Well, I have to say that I did not investigate much on Dynaloader. I >> thing I >> missed a step before reading perldoc Dynaloader. >> If somebody has an hint (or an URL?, manpage?) for me starting at >> understanding this process, I would be grateful ! > > > > You should read up on XS, the glue mechanism between Perl and C. The > book "Advanced Perl Programming" from O'Reilly has some great chapters > on the subject. You might also want to see the perl man pages on XS > (perlxstut and perlxs). http://world.std.com/~swmcd/steven/perl/ also > has some good information (see "XS Mechanics"). > > XS is not vital to program Perl, it's mainly for linking in external X > libraries (like XML::LibXML does), and to implement some functions in > C for them to be faster. > >
Re: mod_accel reverse proxying?
Philip Mak wrote: > On Fri, 28 Dec 2001, Igor Sysoev wrote: > > I think it should have reverse syntax: > > > > AccelReverse http://127.0.0.1:8001/ / > > > > Or not ? Of course it complicates porting from mod_proxy to mod_accel > > but I think it's clearer then ProxyPassReverse syntax. > > I don't think either order is more clearer than the other, but since > ProxyPassReverse has it like / http://127.0.0.1:8001/, my personal opinion > is that AccelPassReverse should have it in the same order too to avoid > confusion. > On the other hand, I find mod_proxy's syntax weird and support Igor's proposal. Still, either one would be very handy!
mod_deflate warning
I posted a couple of weeks ago about how well the mod_deflate/mod_accel combination works on a front-end HTTP accelerator. I've just discovered a problem that I thought I'd mention here for anyone who's trying this out. It appears that Mozilla-based browsers fail when using gzip encoding with POST requests. I've added DeflateDisableRange "MSIE 4." "Mozilla" to my httpd.conf as a workaround for this bug. The bug appears intermittently, and I haven't yet worked out exactly how to replicate it. However, it's been reported by many of my users and I have experienced it myself, so I'd suggest being wary of this combination.
[ANNOUNCE] Cache::Mmap 0.03
file: $CPAN/authors/id/P/PM/PMH/Cache-Mmap-0.03.tar.gz size: 9454 bytes md5: f28df3400f28b54034a8a684a8e1e923 I strongly advise all users of this module to upgrade to this version if they are using the write() method, and at least version 0.02 otherwise. The next version should come out within the next week or so, and will remove the dependency on Mmap.pm, and use more portable file locking. >From the README: This module provides a shared cache, using a memory mapped file. Very useful for mod_perl applications. If routines are provided which interact with the underlying data, access to the cache is completely transparent, and the module handles all the details of refreshing cache contents, and updating underlying data, if necessary. Changes since version 0.02 Fixed serious bug in write(), which corrupted the cache file when replacing already existing entries Changes since version 0.01 Fixed serious bug in read(), which didn't update the current bucket content size when expiring entries. This caused infinite loops in _find() and _insert(), which have also been fixed, should anything else ever go wrong in a similar way -- Peter Haworth [EMAIL PROTECTED] "Besides, I wasn't trying to help them understand. I was only trying to help them think they understand." -- Larry Wall
re: how to access the perl file from palm top (READ THIS ONE)
[sorry, forgot about the otherpart of this] CGI::WML available from CPAN ... you should be able to port your code quite easily with it. also - you need to set up the mime-type for wml in apache, 1.3.22 and up seem to have it already (don't know about previous versions). hope that helps- grant Grant Babb Email: [EMAIL PROTECTED] Data Junction Corporation Phone: (512) 459-1308 2201 Northland Dr. Fax: (512) 459-1309 Austin, TX 78756-1117 Web: http://www.datajunction.com
re: how to access the perl file from palm top
CGI::WML available from CPAN ... you should be able to port your code quite easily with it. hope that helps- grant
[OT] Re: XML::LibXML
At 16:58 28/12/01, Fred wrote: >I know (guess?) my answer in somwhere linked with Dynaloader. >But I do not find the link between XML::LibXML and libxml2. Do not man have >to specify it somewhere? Where is the link between C libs and Perl? >How come can calls to undefined methods like $self->_parse_file() (in method >XML::LibXML->parse_file()) can be found? Where is the inheritance defined? > >Well, I have to say that I did not investigate much on Dynaloader. I thing I >missed a step before reading perldoc Dynaloader. >If somebody has an hint (or an URL?, manpage?) for me starting at >understanding this process, I would be grateful ! You should read up on XS, the glue mechanism between Perl and C. The book "Advanced Perl Programming" from O'Reilly has some great chapters on the subject. You might also want to see the perl man pages on XS (perlxstut and perlxs). http://world.std.com/~swmcd/steven/perl/ also has some good information (see "XS Mechanics"). XS is not vital to program Perl, it's mainly for linking in external X libraries (like XML::LibXML does), and to implement some functions in C for them to be faster. -- Per Einar Ellefsen [EMAIL PROTECTED]
XML::LibXML
Hi, sorry for this question that is not directly related to mod_perl, rather to perl itself. I use XML::LibXML, that I found on http://www.xml.com, and it matches my needs. Because it might (surely!) be good code structure examples, I had a look at the module. There comes my question : I do not understand how it works. I know (guess?) my answer in somwhere linked with Dynaloader. But I do not find the link between XML::LibXML and libxml2. Do not man have to specify it somewhere? Where is the link between C libs and Perl? How come can calls to undefined methods like $self->_parse_file() (in method XML::LibXML->parse_file()) can be found? Where is the inheritance defined? Well, I have to say that I did not investigate much on Dynaloader. I thing I missed a step before reading perldoc Dynaloader. If somebody has an hint (or an URL?, manpage?) for me starting at understanding this process, I would be grateful ! Thanks, Fred
Re: CGI module bug, Internet Explorer 6 problems and workaround...
> Hope this helps any people who encounter the same problem. Though it of course raises the > question, is the XHTML incorrect in someway to cause IE to barf, or is IE barfing incorrectly? I do work on a product (http://www.mkdoc.com) which outputs mainly valid XHTML, and it works fine with any browser basically. Have you tried to use an XHTML validator on the XHTML code that is being generated? Cheers, -- IT'S TIME FOR A DIFFERENT KIND OF WEB Jean-Michel Hiver - Software Director [EMAIL PROTECTED] +44 (0)114 221 4968 VISIT HTTP://WWW.MKDOC.COM
Re: What phase am I in?
--On jeudi 20 décembre 2001 16:10 -0600 Dave Rolsky <[EMAIL PROTECTED]> wrote: > On Thu, 20 Dec 2001, Perrin Harkins wrote: > >> > I've looked through the mod_perl docs and guide and am unable to find >> > something that I can use in a handler to figure out what the current >> > phase is. This seems like such an obvious thing that I can't believe >> > it doesn't exist. Therefore I will conclude that I'm completely >> > blind. Anyone care to open my eyes? >> >> http://mathforum.org/epigone/modperl/liphortwa/Pine.LNX.4.10.99092112175 >> 10.5 [EMAIL PROTECTED] >> >> It's called current_callback(). > > Grr, its not documented when I do 'perldoc Apache'. It is now. -- Eric Cholet
Re: mod_accel reverse proxying?
On Fri, 28 Dec 2001, Igor Sysoev wrote: > Yes, it doesn't. It's difficult to figure proxied URL parts in mod_rewrite > so I have to make explicit directive to specify reverse rewrite. > I will make it today or tomorrow. Great! > I think it should have reverse syntax: > > AccelReverse http://127.0.0.1:8001/ / > > Or not ? Of course it complicates porting from mod_proxy to mod_accel > but I think it's clearer then ProxyPassReverse syntax. I don't think either order is more clearer than the other, but since ProxyPassReverse has it like / http://127.0.0.1:8001/, my personal opinion is that AccelPassReverse should have it in the same order too to avoid confusion.
