.
Oh well, back to the drawing board.
Thanks
-Chris
From: Marcus Don [mailto:m...@names.co.uk]
Sent: Thursday, May 30, 2013 12:00 PM
To: Chris Faust
Cc: modperl@perl.apache.org
Subject: Re: Help on debugging print problem
I suspect you can just to this...
my $size = -s
t; my $body_len = calculate_body_len();
> $r->set_content_length($body_len);
> $r->rflush;
>
> Which just did nothing.
>
> Thx
> -Chris
>
> From: Marcus Don [mailto:m...@names.co.uk]
> Sent: Thursday, May 30, 2013 9:12 AM
> To: Chris Faust
> Cc: modper
>set_content_length($body_len);
$r->rflush;
Which just did nothing.
Thx
-Chris
From: Marcus Don [mailto:m...@names.co.uk]
Sent: Thursday, May 30, 2013 9:12 AM
To: Chris Faust
Cc: modperl@perl.apache.org
Subject: Re: Help on debugging print problem
At a guess, I'd say you
27;);
> $r->err_headers_out->add('Content-Disposition' =>
> 'attachment; filename="report.pdf"');
> $r->print($output);
> }
>
> I've never had a problem before using the above until trying to do it on a
&g
};
close(PDF);
$r->content_type('application/pdf');
$r->err_headers_out->add('Content-Disposition' =>
'attachment; filename="report.pdf"');
$r->print($output);
}
I've never had a problem
Hi,
Apache process is segfaulting when I use mod_perl.
It seems to occure when a process send more than 32kB of data in the
RequestRec::print method (not really sure of the 32k limit).
Anybody with the same problem ?
Full bug report with core trace below.
Thanks !
Laurent.
-8
with an
Apache2::RequestRec object $r. It includes the following statement that
calls a print() method:
[[
$r->print("Now is: " . scalar(localtime) . "\n");
]]
But there is no print() method defined in Apache2::RequestRec, and there
is no indication that Apache2::Reque
ing them to be patient and wait until the page is loaded.
>
>
>
> On Wed, Aug 4, 2010 at 7:34 PM, wrote:
>>>
>>>> Error logs are filling up with strange "File does not exist" errors and
>>>>
>>> code
>>>
>>>> i
lling up with strange "File does not exist" errors and
code
is trapping Apache exception:
Apache2::RequestIO::print: (53) Software caused connection abort
These errors are repeatably caused by client breaking the connection
before
page has loaded (page loads slowly becau
not causing connection to time out. User is
clicking a link before javascript finishes and page load completes.
>
> On Wed, Aug 4, 2010 at 7:34 PM, wrote:
> > Error logs are filling up with strange "File does not exist" errors and
> code
> > is trapping Apache except
One approach that comes to mind is to print smaller chunks of the
response and between those check $r->connection->aborted to see if the
connection is still alive. However I don't think you'll be successful
with that approach since the connection is broken while printing to
the
Error logs are filling up with strange "File does not exist" errors and code
is trapping Apache exception:
Apache2::RequestIO::print: (53) Software caused connection abort
These errors are repeatably caused by client breaking the connection before
page has loaded (page lo
Angel Morales wrote:
Greetings,
We recently upgraded to mod_perl2 and we started seeing this error:
Apache2::RequestIO::print: (103) Software caused connection abort at ...
The line has a $r->print(), we've tried everything, including eval() the
line but nothing helps.
Server
hrieb Angel Morales:
> Greetings,
>
> We recently upgraded to mod_perl2 and we started seeing this error:
>
> Apache2::RequestIO::print: (103) Software caused connection abort at ...
>
> The line has a $r->print(), we've tried everything, including ev
Greetings,
We recently upgraded to mod_perl2 and we started seeing this error:
Apache2::RequestIO::print: (103) Software caused connection abort at ...
The line has a $r->print(), we've tried everything, including eval() the
line but nothing helps.
Server Version: Apache/2.0.52
Torsten Förtsch,
You are awesome! That was it.
I had a line in there just before '$r->print($tmpl->output)'
$r->content_type("text/html; charset=ISO-8859-1\n\n");
I removed the two \n and now, it is working great with both IE and FF..
Really, truly appreciat
he following error in the apache error log. And, IE hangs in a
> 'working' loop, without displaying the page.
>
> [Thu May 20 03:01:08 2010] [error] Apache2::RequestIO::print: (103)
> Software caused connection abort at ...util.pm line 855
>
> The line it is com
p, without displaying the page.
[Thu May 20 03:01:08 2010] [error] Apache2::RequestIO::print: (103)
Software caused connection abort at ...util.pm line 855
The line it is complaining about is
$r->print($tmpl->output);
The strange part is that this error shows up ONLY when browsing via IE
Hello,
I started to see the following when I setup a new server on CentOS 5.4
and installed perl modules from CPAN on Dec. 4:
Denis Banovic wrote:
This is from the error_log from the RedHat 5 Production machine:
Apache2::RequestIO::print: (103) Software caused connection abort at
The
Hi Morten,
Thanks a lot,
By putting an eval around the code I found out, that the segfault was produced
by next request to the same child after the $r->print failed.
$r->print is still failing from time to time, but it's not producing segfaults
anymore!
Thanks
Denis
-Ur
Earlier when we run on mod_perl1.99 and the redhat stack it worked fine.
But then we had other worries :-)
--
Morten Bjoernsvik, Developer, Decision Analytics
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: 23. november 2009 09:46
To: mod_perl list
Subject
Denis Banovic wrote:
Hi Willian,
Thanks for your checklist, I've run through it, segfaults still there...
Right now it takes less then a minute from apache restart to the first segfault.
This is from the error_log from the RedHat 5 Production machine:
Apache2::RequestIO::print: (103) Sof
Hi Willian,
Thanks for your checklist, I've run through it, segfaults still there...
Right now it takes less then a minute from apache restart to the first segfault.
This is from the error_log from the RedHat 5 Production machine:
Apache2::RequestIO::print: (103) Software caused connection
This is the list of stuff I usually start with when I get a problem
that doesn't seem to be tied to a particular code path.
* code path - perhaps a particular code path is only being exercised
rarely, and it has a bug
* forking - when child dies, all open descriptors in it's name space
also ge
from /usr/lib/libapr-0.so.0
The content-type is set by
$r->content_type("text/html; charset=iso-8859-1") but this is not what is
causing him to segfault...
By try and error I've figured out that the segfault happens when I do a
$r->print($mypagecontent);
I've
On Wed, Oct 22, 2008 at 6:28 AM, André Warnier <[EMAIL PROTECTED]> wrote:
> I would not ask, if there were not sometimes really many of these being
> executed over and over again. I figure it may be worth knowing if one of
> the forms above (or another one I haven't tried) is really better than
>
On Wed, Oct 22, 2008 at 5:28 AM, André Warnier <[EMAIL PROTECTED]> wrote:
> another one I haven't tried
how about an Inline::C function that wraps printf and takes $var2 as
an argument, and another that takes $var1 as an argument which
overwrites the static buffer allocated for the format string?
eding decade.
> Now, my question is, considering the way perl handles these things
> internally, how do these different forms compare in terms of eficiency ?
Perl sorts all of this out at compile time, so:
print "$var1 text"
and
print $var1.' text'
are represented by
Hi.
This is probably a question better asked to the perl monks or similar,
but if there are any of them lurking around here, it would save me a
subscription.
In various programs, I do a lot of printing, for results or for logging.
Really many print statements, in forms such as :
print OUT
Hi,
What is the easist way to retrieve and print the html headers within
mod_perl.
Can we do it using CGI.pm
Thanks
--
View this message in context:
http://www.nabble.com/print-headers-tp17181544p17181544.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
Michael Peters wrote:
Robert L Hicks wrote:
[error] Apache2::RequestIO::print: (104) Connection reset by peer at
/usr/lib/perl5/Template.pm line 178
Doesn't it just mean that the user hit the stop button before finishing the
download of the page? So you were in the middle of writing t
Robert L Hicks wrote:
> [error] Apache2::RequestIO::print: (104) Connection reset by peer at
> /usr/lib/perl5/Template.pm line 178
Doesn't it just mean that the user hit the stop button before finishing the
download of the page? So you were in the middle of writing to the pipe when
[error] Apache2::RequestIO::print: (104) Connection reset by peer at
/usr/lib/perl5/Template.pm line 178
Has anyone seen that before and/or would you know what I need to look at?
Robert
Of course... I saw that - but it didn't sync in... Thanks!
-Original Message-
From: Michael Peters [mailto:[EMAIL PROTECTED]
Sent: Friday, January 04, 2008 1:37 PM
To: Kate Yoak
Cc: modperl@perl.apache.org
Subject: Re: print
Kate Yoak wrote:
> I keep running into met
Kate Yoak wrote:
> I keep running into methods not implemented where documentation says
> they are. Is it something about me or a common problem?
One of the new features of mod_perl 2 is less memory usage by default. It does
this by not loading some of those extra methods unless you ask for them.
I keep running into methods not implemented where documentation says they
are. Is it something about me or a common problem?
sub handler{
my $r = shift;
$r->print("hello");
}
fails with "Can't locate object method print via package
Apache2::RequestRec"
On Dec 23, 2007, at 1:53 AM, [EMAIL PROTECTED] wrote:
I think the print magic only happens if you are running under
SetHandler perl-script, and not if you are running under SetHandler
modperl.
Ah, that seems to be it.
I never used perl-script ; I went straight for modperl when i did the
wrote:
> Quoting Perrin Harkins <[EMAIL PROTECTED]>:
>
> > On Dec 22, 2007 5:21 PM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> >> On Dec 22, 2007, at 4:47 PM, Perrin Harkins wrote:
> >> > By the way, if you just call print() normally it should all be
t it says, i.e. setting PerlOptions +GlobalRequest?
>
> By the way, if you just call print() normally it should all be grabbed
> by mod_perl anyway. Is there some reason you need to call $r->print()
> instead?
>
> - Perrin
>
Quoting Perrin Harkins <[EMAIL PROTECTED]>:
On Dec 22, 2007 5:21 PM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
On Dec 22, 2007, at 4:47 PM, Perrin Harkins wrote:
> By the way, if you just call print() normally it should all be grabbed
> by mod_perl anyway. Is there some
On Dec 22, 2007 5:21 PM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> On Dec 22, 2007, at 4:47 PM, Perrin Harkins wrote:
> > By the way, if you just call print() normally it should all be grabbed
> > by mod_perl anyway. Is there some reason you need to call $r->print()
&g
On Dec 22, 2007, at 4:47 PM, Perrin Harkins wrote:
By the way, if you just call print() normally it should all be grabbed
by mod_perl anyway. Is there some reason you need to call $r->print()
instead?
I thought it only does that if you bind STDOUT the right way on
compile time, otherw
On Dec 22, 2007 4:40 PM, Will Fould <[EMAIL PROTECTED]> wrote:
> "Global $r object is not available. Set:\n\tPerlOptions +GlobalRequest\nin
> httpd.conf"
And did you try what it says, i.e. setting PerlOptions +GlobalRequest?
By the way, if you just call print() nor
Thanks Colin,
When I try that within a package and just use:
$r->print( "Hello");
I still get:
"Global $r object is not available. Set:\n\tPerlOptions +GlobalRequest\nin
httpd.conf"
But, I do get the correct response when I use $mnh::r->print( "Hello"
Will Fould wrote:
Is this a reasonable approach? Is it typical to refer to the request
object by package name rather than try to painfully re-factor all
packages and subs to accept $r as a passed reference?
I don't know if this will help your re-factoring, but you should note
you can always g
Greeting: I've got a style-related question:
We have dozens of application packages running neatly under MP2 but that all
still use 'print' and also call other packages to print needed headers, etc.
I've created a single handler package (called 'mnh') that now
I found another component to the seg fault. I am using a dynamically linked
mod_deflate output filter as well (will test with static). I get no seg
fault when I comment out the DEFLATE line in the Apache config. (Sorry, I
hadn't noticed this piece of the puzzle.)
LoadModule deflate_module
eems to be the use of LWP::UserAgent
within a bucket brigade filter. The seg fault occurs if Perl hasn't yet
loaded this module (and friends). After the filter runs successfully - seg
fault. Interestingly though, the other factors described are all necessary:
CGI.pm header(), the print statem
I'm getting seg faults within "print" of ModPerl::Registry script while
using an output filter handler. The output filter is run during the
script's "print" statement when the printed string is > ~8kb. Debugging
shows the seg fault occurs AFTER the output filter h
On Mon, 30 Oct 2006 13:15:32 -0700
Harry Plate <[EMAIL PROTECTED]> wrote:
> Peter,
>
> >
> > You can also temporarily disable SELinux by doing:
> >
> > echo '0' > /selinux/enforce
> >
>
> Bingo! That was it!
>
> So, I don't see any SELinux configuration (within Webmin, at least).
> I need to
Peter,
>
> You can also temporarily disable SELinux by doing:
>
> echo '0' > /selinux/enforce
>
Bingo! That was it!
So, I don't see any SELinux configuration (within Webmin, at least). I need
to learn more about it ... How does one disable it at boot time? That would
be a good temporary solut
SELinux is certainly included in RHEL 4 (though it is an option at install time whether it is enabled or not). Check your message log for avc failures. e.g.:kernel: audit(1162240773.996:667): avc: denied { write } for pid=23025 comm="httpd" name="dprof" dev=dm-0 ino=24282699 scontext=root:system
On Mon, 2006-10-30 at 12:47 -0700, Harry Plate wrote:
> *** Cannot open log file, Permission denied at /var/www/cgi-bin/test.pl...
[...]
> Note the folder and file permissions are wide open; so I would next expect
> that the unix fs is *not* the one that is complaining...
I think it probably is yo
> You ought to test if the file is really open first, and you will hopefully
> get a more helpful error message:
>
> open(LOGFILE, ">>junk.log") or die "Cannot open logfile, $!";
>
Good suggestion; so I add the "die" and I get the error:
*** Cannot open log file, Permission denied at /var/www/
what error is the open giving?
> open (LOGFILE, ">>junk.log") ;
open (LOGFILE, ">>junk.log")
or die "Couldn't open junk.log for appending : $!";
Also, it may be that somewhere LOGFILE is defined as a constant, and so
the bare filehandle LOGFILE is being interpreted as LOGFILE()
Rather use
You ought to test if the file is really open first, and you will hopefully
get a more helpful error message:
open(LOGFILE, ">>junk.log") or die "Cannot open logfile, $!";
(LOGFILE, ">>junk.log") ;
Ea print on LOGFILE results in the error:
...print() on closed filehandle LOGFILE at /var/www/cgi-bin/test.pl
The "WS" system has no problems writing to LOGFILE , whereas the enterprise
system fails.
The /var/log folder permissions are
ork:
>
>#!/usr/bin/perl -Tw
>
>use strict;
>
>print "Content-type: text/plain\n\n";
>
>my $fh = select;
>print $fh "hi\n";
>
>results in: Can't use string ("main::STDOUT") as a symbol ref while
>&quo
ldn't get it to work:
#!/usr/bin/perl -Tw
use strict;
print "Content-type: text/plain\n\n";
my $fh = select;
print $fh "hi\n";
results in: Can't use string ("main::STDOUT") as a symbol ref while
"strict refs" in
On Tue, 21 Feb 2006 11:22:22 -0600
Chris Werner <[EMAIL PROTECTED]> wrote:
> Frank Wiles Wrote:
>
> >
> http://perl.apache.org/docs/1.0guideporting.html#STDIN__STDOUT_and_STDERR_st
> reams
>
> Dead link?
>
Grrr... sometimes I hate my mail client. Let's try the shortened
version. :)
ht
Title: RE: Can't print to selected filehandle?
Frank Wiles Wrote:
> http://perl.apache.org/docs/1.0guideporting.html#STDIN__STDOUT_and_STDERR_streams
Dead link?
On Tue, 21 Feb 2006 11:58:37 -0500
Scott Gifford <[EMAIL PROTECTED]> wrote:
> Any idea why this works from the command-line, but not from within
> mod_perl?
>
> #!/usr/bin/perl -Tw
>
> use strict;
>
> print "Content-type: text/p
Any idea why this works from the command-line, but not from within
mod_perl?
#!/usr/bin/perl -Tw
use strict;
print "Content-type: text/plain\n\n";
local *FH = select;
print "FH: ",*FH,"\n";
print FH "Printing to FH\n"
Hi
I have some questions regarding mod_perl's implementation of
Apache::print(), especially relating to Apache 1.3's "Timeout" directive.
To start of, if I look at the documentation for the "Timeout" directive
(http://httpd.apache.org/docs/1.3/mod/core.h
;[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, December 21, 2005 10:15 AM
Subject: Re: $r->print doesn't work in Apache2/MP2/Libapreq2?
On Wed, 21 Dec 2005 10:06:29 -0600
"Harry Zhu" <[EMAIL PROTECTED]> wrote:
sub handler {
my $r = Apache2::Request->new(shift);
my %ins
On Wed, 21 Dec 2005 10:15:49 -0600
Frank Wiles <[EMAIL PROTECTED]> wrote:
> You want to do this instead:
>
> sub handler {
> my $r = shift;
> my $req = Apache2::Request->new( $r );
> my %ins = &process_input($r);
>
> $r->
On Wed, 21 Dec 2005 10:06:29 -0600
"Harry Zhu" <[EMAIL PROTECTED]> wrote:
>
> sub handler {
> my $r = Apache2::Request->new(shift);
> my %ins = &processInput($r);
> ...
> $r->print($html);
> return OK;
> }
>
> Can't locate
That's because the $r you get from shift isn't interchangable with the
$r you get from Apache2::Request (which I think is deprecated anyway).
Try doing
sub handler {
my $r = shift;
my $q = Apache2::Request->new($r);
my %ins = &processInput($q);
...
$r->print($html);
ret
sub handler {
my $r = Apache2::Request->new(shift);
my %ins = &processInput($r);
...
$r->print($html);
return OK;
}
Can't locate auto/Apache2/Request/print.al in @INC (@INC contains:
/www/modperl /usr/local/lib/perl5/5.8.7/i686-linux
/usr/local/lib/perl5/5.8.7 /usr/
Fedora Core 4
httpd-2.0.54-10
mod_perl-2.0.0-0.rc5.3
nph mod_perl script
If I user $r->print to print the response to the client, it returns that
it sent more bytes than length($write_buffer) and the JPEG, which is
part of the response, is bad if the response header contains a
Cont
In the second example I have already appended "\r\n" to the write buffer.
So it really is:
$write_buffer .= "\r\n";
$r->print($write_buffer);
$r->print($jpeg);
$r->print("\r\n\r\n");
I try to write the same data to the client. In one case I write it as
on
Hi Christopher -
I don't know if it's a typo but this:
$write_buffer .= "\r\n" . $jpeg . "\r\n\r\n";
$r->print($write_buffer);
is not the same as this:
$r->print($write_buffer);
$r->print($jpeg);
$r->print("\r\n\r\n");
since the lat
t_filename\"\r\n"
otherwise, I do not include this tag in the header.
I am creating the buffer as I go (appending header tags). I append the
separator and the JPEG:
$write_buffer .= "\r\n" . $jpeg . "\r\n\r\n";
And then send the buffer to the client:
$r->print(
Ok, sorry for the previous two (rather horrible) mails it's getting to
be the time of night where (really bad) good ideas abound, so I'll just
leave this information before going to bed:
mod_perl-1.27 according to gentoo portage, mod_perl 1.29 according to my
Apache server string.
perl-5.8.5
Arne
> You don't say which mod_perl version you are using, Arne.
D'oh! I really should've remembered to add that info.
So basically Apache does everything I want on it's own. How clever and,
well, obvious. Thanks for bothering with what I honestly should've
figured out on my own.
Arne
:wq
Arne Skjaerholt wrote:
Hello all,
I'm currently working on a project where I've decided to subclass
Apache, and one of the methods I've decided to overload is the print
method (so that my main module decides when data actually gets printed,
not user modules). Now, I'd like
Hello all,
I'm currently working on a project where I've decided to subclass
Apache, and one of the methods I've decided to overload is the print
method (so that my main module decides when data actually gets printed,
not user modules). Now, I'd like to also override the built
I'm having trouble getting STDERR output to show up in the apache
error_log. This is supposed to work automagically, right? Using
$r->log_error() works fine, but sometimes it is really inconvenient when
debugging modules that aren't mp aware. Is there a module I need to use
or a method I need t
Boysenberry Payne wrote:
I'm using mod_perl with Apache::Register in the httpd.conf file.
The only way I can get output to my web browser is by using
my $r = Apache->request;
$r->print( "Output" );
This is regardless of the Content Type declaration.
If I try printing using a s
I'm using mod_perl with Apache::Register in the httpd.conf file.
The only way I can get output to my web browser is by using
my $r = Apache->request;
$r->print( "Output" );
This is regardless of the Content Type declaration.
If I try printing using a standard print command I g
I'm using mod_perl with Apache::Register in the httpd.conf file.
The only way I can get output to my web browser is by using
my $r = Apache->request;
$r->print( "Output" );
This is regardless of the Content Type declaration.
If I try printing using a standard print command I g
> Sure, +1 then for your patch.
done
> But should
> http://perl.apache.org/docs/2.0/api/Apache/RequestIO.html#C_print_
> mention that 0E0 nuance?
done
--Geoff
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://
Geoffrey Young wrote:
It certainly is an API change. At least it makes the API inconsistent
since now:
$r->print("");
and
print "";
are not the same under modperl.
um, how do you figure? the new tests show that those two calls are exactly
the same - they both return &#x
> It certainly is an API change. At least it makes the API inconsistent
> since now:
>
> $r->print("");
>
> and
>
> print "";
>
> are not the same under modperl.
um, how do you figure? the new tests show that those two calls are exactly
t
t's really an API change and I don't think it's as complex as
all of that...
It certainly is an API change. At least it makes the API inconsistent
since now:
$r->print("");
and
print "";
are not the same under modperl.
Moreover, failures are not the same as
#x27;t think it's really an API change and I don't think it's as complex as
all of that...
the perldoc for print() says it returns true on success, whereas the perldoc
for printf(), send(), read() make no such claims.
so, the change to print() would be to make it behave the same
Geoffrey Young wrote:
Tuomo Salo wrote:
Under mod_perl2 the return value of print seems to be the number of
bytes printed. I run across a legacy app (a registry script), that
frequently used the following idiom:
print(CGI::redirect("url_to_error_page")) and return if $error;
Whi
Tuomo Salo wrote:
> Under mod_perl2 the return value of print seems to be the number of
> bytes printed. I run across a legacy app (a registry script), that
> frequently used the following idiom:
>
>
> print(CGI::redirect("url_to_error_page")) and return if $
Tuomo Salo wrote:
Under mod_perl2 the return value of print seems to be the number of
bytes printed. I run across a legacy app (a registry script), that
frequently used the following idiom:
[...]
This behaviour is nearly impossible to notice, since the redirection
will happen as usual. The
Under mod_perl2 the return value of print seems to be the number of
bytes printed. I run across a legacy app (a registry script), that
frequently used the following idiom:
print(CGI::redirect("url_to_error_page")) and return if $error;
While this is obviously a stupid way to write, i
Rathna N wrote:
Hi,
I'm new to Apache/mod-perl. I hope I'm asking this question in the right forum.
When I executed a script having " print print "Hello"; " at shell, it
returns "Hello1",
but when I executed thru mod-perl it returns "Hello5"
Paint me purple and color me an idiot, nevermind, I found my problem.
thanks yall anyway.
On Thu, 18 Nov 2004 20:13:19 -0700, Robert Ferney <[EMAIL PROTECTED]> wrote:
> I am experancing the following undesirable behavior.
>
> My code looks somethign like this..
>
> $r->
Hi,
I'm new to Apache/mod-perl. I hope I'm asking this question in the right forum.
When I executed a script having " print print "Hello"; " at shell, it
returns "Hello1",
but when I executed thru mod-perl it returns "Hello5".
CODE SNIPPET:
I am experancing the following undesirable behavior.
My code looks somethign like this..
$r->print("Some htmlish bits");
$r->rflush;
$r->sendfile("/path/to/somefile");
$r->print("Some more htmlish bits");
$r->rflush;
$r->sendfile("/path/to/s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 06 February 2004 11:54, Manuel Gil Perez wrote:
> authentication). How can I print in the client web page his certificate
> complete??
with
SSLOptions +ExportCertData
the client and the server cert are stored in pem format
Hello there,
On Fri, 6 Feb 2004, Manuel Gil Perez wrote:
> Excuse me for my question, but it's a dude for this mailing list.
Please refer to
Reporting bugs: http://perl.apache.org/bugs/
73,
Ged.
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/
x27;ve the following PERL code and I get all variables in text format as
i.e. SSL_CLIENT_I_DN_O -> euro6ix and SSL_CLIENT_M_SERIAL -> 0106. How can I
get the SSL_CLIENT object??
foreach my $var (keys %ENV)
{
print "$var -> $ENV{$var} \n";
}
Thanks.
- Original Message -
Hello there,
On Fri, 6 Feb 2004, Manuel Gil Perez wrote:
> I've install/configure an Apache server with SSL support (and client
> authentication). How can I print in the client web page his certificate
> complete??
This is the mod_perl Mailing List. Your question does not appe
Something like this should do the trick...
print `openssl x509 -text < CERTIFICATE.PEM`;
- Original Message -
From: "Manuel Gil Perez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 06, 2004 12:54 PM
Subject: Print X.509 certificate
&g
Hi all,
I've install/configure an Apache server with SSL support (and client
authentication). How can I print in the client web page his certificate
complete??
Thanks and regards,
--
Manuel Gil Perez
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apach
1 - 100 of 136 matches
Mail list logo
