22 lines
1.1 KiB
Plaintext
22 lines
1.1 KiB
Plaintext
$OpenBSD: patch-polipo_texi,v 1.1 2005/09/24 17:58:23 bernd Exp $
|
|
--- polipo.texi.orig Fri Sep 23 20:19:08 2005
|
|
+++ polipo.texi Sat Sep 24 19:00:33 2005
|
|
@@ -1245,7 +1245,7 @@ from the server. If the latter arrives,
|
|
the rest of the POST request@footnote{This, of course, is only part of
|
|
the story. Additionally, the server is not required to reply with
|
|
@samp{100 Continue}, hence the client must implement a timeout.
|
|
-Furthermore, according to the obsolete RFC@tie{}2068, the server is
|
|
+Furthermore, according to the obsolete RFC@w{}2068, the server is
|
|
allowed to spontaneously send @samp{100 Continue}, so the client must
|
|
be prepared to ignore such a reply at any time.}.
|
|
|
|
@@ -1353,7 +1353,7 @@ or because it was revalidated.
|
|
If @code{cacheIsShared} is false (the default), Polipo will ignore the
|
|
server-side @samp{Cache-Control} directives @samp{s-maxage} and
|
|
@samp{proxy-must-revalidate}. This is highly desirable behaviour, but
|
|
-happens to violate RFC@tie{}2616 if the cache is shared among multiple
|
|
+happens to violate RFC@w{}2616 if the cache is shared among multiple
|
|
users.
|
|
|
|
If @code{mindlesslyCacheVary} is true, the presence of a Vary header
|