Apache2-PodBrowser

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    If the POD file name doesn't contain a dot (".") the last path component
    is stripped off to get the directory name.

    Note that you need to write the package name again. You also need to
    either escape the semicolons as in
    "src="Apache2%3A%3APodBrowser/torsten-foertsch.jpg"" or put a "./" in
    front of the link.

    A note about the content type of linked documents. "Apache::PodBrowser"
    does not enter a new request cycle to ship these documents. So, the
    normal Apache Content-Type guessing does not take place.
    "Apache::PodBrowser" knows a few file name extensions ("png", "jpg",
    "jpeg", "gif", "js", "pdf" and "html"). For those it sends the correct
    Content-Type headers. All other documents are shipped as
    "application/octet-stream".

    If a document needs a different Content-Type header it can be passed as
    CGI parameter:

     src="Apache2%3A%3APodBrowser/torsten-foertsch.jpg?ct=text/plain"

lib/Apache2/PodBrowser.pm  view on Meta::CPAN

If the POD file name doesn't contain a dot (C<.>) the last path component
is stripped off to get the directory name.

Note that you need to write the package name again. You also need to
either escape the semicolons as in
C<src="Apache2%3A%3APodBrowser/torsten-foertsch.jpg"> or put a C<./>
in front of the link.

A note about the content type of linked documents. C<Apache::PodBrowser>
does not enter a new request cycle to ship these documents. So, the normal
Apache Content-Type guessing does not take place. C<Apache::PodBrowser> knows
a few file name extensions (C<png>, C<jpg>, C<jpeg>, C<gif>, C<js>,
C<pdf> and C<html>). For those it sends the correct Content-Type headers.
All other documents are shipped as C<application/octet-stream>.

If a document needs a different Content-Type header it can be passed as
CGI parameter:

 src="Apache2%3A%3APodBrowser/torsten-foertsch.jpg?ct=text/plain"

The link above will ship the image as C<text/plain>.



( run in 0.243 second using v1.01-cache-2.11-cpan-26ccb49234f )