App-Wallflower

 view release on metacpan or  search on metacpan

bin/wallflower  view on Meta::CPAN

    404 /images/perldancer-bg.jpg
    404 /images/perldancer.jpg
    200 /javascripts/jquery.js => /tmp/output/javascripts/jquery.js [248235]

Note that URLs with a path ending in a C</> are considered directories
and have the default I<index> filename appended, and that wallflower will
behave unpredictably if the site contains pages accessible through URLs
ending both in F<foo> and F<foo/>. This is arguably a bug, but it's
unclear where to fix it, or if it can be fixed at all. See
L<Wallflower::Tutorial/URI SEMANTICS COMPARED TO DIRECTORY SEMANTICS> for
background on this.

Any response with a status other than C<200> will be logged,
but not saved. Responses with a C<301> status (moved) are followed.

B<wallflower> sends the C<If-Modified-Since> header if the target
file for a given URL already exists in the destination directory.
If the application replies with a C<304> status, the file is not
modified. If the 304 response contains a C<Content-Type> header
and I<--follow> is enabled, the file will be searched for more
links to follow.

t/file-01.css  view on Meta::CPAN

@import "foo.css";
@import "bar.css";
h1 {
    background: url(/img.png);
}

h2 {
    background: url("img_qq.png");
}

h3 {
    background: url('../img_q.png');
}

h4 {
    background: url(http://example.com/ex.png);
}



( run in 1.735 second using v1.01-cache-2.11-cpan-d8267643d1d )