An xlate configuration module shouldn't mess with BO_WXLATE;

ap_set_content_xlate() takes care of that detail.

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

diff --git a/modules/experimental/mod_charset_lite.c b/modules/experimental/mod_charset_lite.c
index 03eb6d69390a04aba243e5f239a3e1ca2d63b9f5..59e6e6d8a326305eba5e96c9daf4dec47b64e491 100644 (file)
--- a/modules/experimental/mod_charset_lite.c
+++ b/modules/experimental/mod_charset_lite.c
@@ -238,13 +238,6 @@ static int find_code_page(request_rec *r)
         return HTTP_INTERNAL_SERVER_ERROR;
     }
 
-    rv = ap_bsetopt(r->connection->client, BO_WXLATE, &r->rrx->to_net);
-    if (rv != APR_SUCCESS) {
-        ap_log_error(APLOG_MARK, APLOG_ERR, rv, r->server,
-                     "can't set translation; BO_WXLATE->%d\n", rv);
-        return HTTP_INTERNAL_SERVER_ERROR;
-    }
-
     return DECLINED;
 }