Thanks, Tom. Yep, this does the job just fine and allows me to send
the Content-type later:
print "HTTP/1.1 OK\n";
Is ignoring PerlSendHeader considered a feature? ;)
-gm
On Tue, 20 Nov 2001, Tom Mornini wrote:
> This took me a LONG time to deal with when I was new to mod_perl...
>
> Apac
On Tue, 20 Nov 2001, Rob Bloodgood wrote:
> > You must include code to deal with the fact that you may have already
> > opened a popup window. Something like this:
>
> That is simply not true. window.open() with a named window ('popupwin', in
> your example) ALWAYS reuses that window, on every
I need mod_perl to not send the Content-type header when a program is
run. Despite the "Off" value of the "PerlSendHeader" variable in
httpd.conf, the header is still being sent.
This test program still sends an extraneous Content-type header:
print "Content-type: text/html\n\n";
print "He
On Tue, 20 Nov 2001, Alessandro Forghieri wrote:
> Greetings.
>
> [...]
> > > This documentation patch addresses the single thread snafu on Win32.
> > > Comments, corrections and additions (even subtractions)
> > >welcome. (Also on the hot topic of the day: where in the doc does this
> fit?)
> >
At 18.32 -0500 11/20/2001, Robert Landrum wrote:
>> >If that is the case, My::Special::Module won't be loaded and compiled until the
>very first time that someone hits /whatever.
>>
>>Just about EVERY module we use has a 'PerlModule' call to it, outside any enclosing
>blocks. Although I do have
> If you preload, It's not going to put the module into %INC.
> Otherwise Apache::StatINC would intentionally overwrite that shared
> memory and destroy the purpose for using PerlModule in the first
> place.
...and that's why you shouldn't use StatINC on a production server. There
is no magic ab
>
> >If that is the case, My::Special::Module won't be loaded and
>compiled until the very first time that someone hits /whatever.
>
>Just about EVERY module we use has a 'PerlModule' call to it,
>outside any enclosing blocks. Although I do have 'PerlHandler'
>directives in and blocks, the m
At 18.02 -0500 11/20/2001, Robert Landrum wrote:
>At 2:31 PM -0800 11/20/01, David Pisoni wrote:
>> >We have been doing development using mod_perl, but finding that Apache::StatINC
>was not working as expected (i.e., we needed to restart the web server in order to
>see our module changes in effe
At 2:31 PM -0800 11/20/01, David Pisoni wrote:
> >We have been doing development using mod_perl, but finding that
>Apache::StatINC was not working as expected (i.e., we needed to
>restart the web server in order to see our module changes in
>effect.) Our apache config files preload all necessa
Hello,
I hate to keep banging this old drum, but since I was able to reproduce this problem
(but not solve it), I figured I'd recycle it again. Perrin said earlier that this was
fixed in 1.26, but I am indeed using 1.26 and the problem persists. Stas suggested
upgrading perl to 5.6.1 -- I di
> You must include code to deal with the fact that you may have already
> opened a popup window. Something like this:
That is simply not true. window.open() with a named window ('popupwin', in
your example) ALWAYS reuses that window, on every browser I've ever been
able to test. The second call
Hey,
Apache::ASP v2.29 has been released, CHANGES below, and you can
get it in your local CPAN, or:
http://www.perl.com/CPAN-local/modules/by-module/Apache/
There are some major bugs fixed in this release, that stem
from new work in the 2.25 release. These bugs are about empty
$Sessions not
On Mon, 19 Nov 2001, Ian @ International Sports Agnecy wrote:
if you telnet to port 80 and issue a head request manually, what does the
server report exactly? it should list the modules you have properly
installed.
gedanken
I'm having a bit of a problem getting everything to work right.
Ever
Off topic but in the interests of, if not less popup windows, then at
least less broken ones:
You must include code to deal with the fact that you may have already
opened a popup window. Something like this: