Navigation Menu

Skip to content

Commit

Permalink
fixed a few more links
Browse files Browse the repository at this point in the history
  • Loading branch information
kraih committed Jan 11, 2015
1 parent a4152c8 commit c7addc2
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion lib/Mojo/Content/Single.pm
Expand Up @@ -104,7 +104,7 @@ implements the following new ones.
$single = $single->asset(Mojo::Asset::Memory->new);
The actual content, defaults to a L<Mojo::Asset::Memory> object with
C<auto_upgrade> enabled.
L<Mojo::Asset::Memory/"auto_upgrade"> enabled.
=head2 auto_upgrade
Expand Down
2 changes: 1 addition & 1 deletion lib/Mojo/IOLoop/Delay.pm
Expand Up @@ -196,7 +196,7 @@ and the active event counter reached zero, L</"steps"> will continue.
Arguments passed to the returned callback are spliced with the given offset
and length, defaulting to an offset of C<1> with no default length. The
arguments are then combined in the same order C</"begin"> was called, and
arguments are then combined in the same order L</"begin"> was called, and
passed together to the next step or L</"finish"> event.
# Capture all arguments
Expand Down
2 changes: 1 addition & 1 deletion lib/Mojolicious/Guides/FAQ.pod
Expand Up @@ -144,7 +144,7 @@ variable to change this value.

This is a very similar protection mechanism to the one described in the
previous answer, but a little more specific. It limits the maximum length of
any C<\x0d\x0a> terminated part of a HTTP message, such as request line,
the C<\x0d\x0a> terminated parts of a HTTP message, such as request line,
status line and headers. This limit is around 10KB by default, you can use the
attributes L<Mojo::Message/"max_line_size"> and
L<Mojo::Headers/"max_line_size"> or C<MOJO_MAX_LINE_SIZE> environment variable
Expand Down

0 comments on commit c7addc2

Please sign in to comment.