Add all the BrowserMatch directives mentioned on the known_client_problems

page.

Submitted by:	Lars Eilebrecht
Reviewed by:	Dean Gaudet

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80155 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/misc/known_client_problems.html b/docs/manual/misc/known_client_problems.html
index e06b4f10fefc957b96b7bcbf9eabf4c3b54d4e27..7bfafaa7ad4fbdedbffb1de865f2dcae34be09c3 100644 (file)
--- a/docs/manual/misc/known_client_problems.html
+++ b/docs/manual/misc/known_client_problems.html
@@ -100,7 +100,7 @@ but will not in any other way change the response.
 of the early pre-releases of the 1.1 JDK.  We think it is fixed in the
 1.1 JDK release.  In any event the workaround:
 <BLOCKQUOTE><CODE>
-BrowserMatch Java1.0 force-response-1.0 <BR>
+BrowserMatch Java/1.0 force-response-1.0 <BR>
 BrowserMatch JDK/1.0 force-response-1.0 
 </CODE></BLOCKQUOTE>