view release on metacpan or  search on metacpan

ChangeLog  view on Meta::CPAN

	* $@ was checked for isa, but isa() was a method call instead of
	an UNIVERSAL::isa function call.

1999-08-16  Andreas J. Koenig  <andreas.koenig@anima.de>

	* ExePlan now executes the plan as a series of function calls
	instead of method calls. Only a little bit benchmarked and seems
	to be a little bit better. Can be switched back to method calls by
	manually setting FUNCTIONAL to false

	* can_utf8 now reflects the protocol. HTTP/1.1 allows UTF-8 unless
	they have an Accept-Encoding header

lib/Apache/HeavyCGI.pm  view on Meta::CPAN

}

sub can_png {
  my Apache::HeavyCGI $self = shift;
  return $self->{CAN_PNG} if defined $self->{CAN_PNG};
  my $acce = $self->{R}->header_in("Accept") || "";
  return $self->{CAN_PNG} = 0 unless $acce;
  $self->{CAN_PNG} = $acce =~ m|image/png|i;
}

sub can_utf8 {
  my Apache::HeavyCGI $self = shift;
  return $self->{CAN_UTF8} if defined $self->{CAN_UTF8};

  # From chapter 14.2. HTTP/1.1

  ##   If no Accept-Charset header is present, the default is that any
  ##   character set is acceptable. If an Accept-Charset header is present,
  ##   and if the server cannot send a response which is acceptable
  ##   according to the Accept-Charset header, then the server SHOULD send
  ##   an error response with the 406 (not acceptable) status code, though

lib/Apache/HeavyCGI.pm  view on Meta::CPAN

Set by the can_gzip method. True if client is able to handle gzipped
data.

=item CAN_PNG

Set by the can_png method. True if client is able to handle PNG.

=item CAN_UTF8

Set by the can_utf8 method. True if client is able to handle UTF8
endoded data.

=item CGI

An object that handles GET and POST parameters and offers the method
param() and upload() in a manner compatible with Apache::Request.
Needs to be constructed and set by the user typically in the
contructor.

=item CHARSET