Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A83BC10234 for ; Thu, 1 Jan 2015 09:24:11 +0000 (UTC) Received: (qmail 68899 invoked by uid 500); 1 Jan 2015 09:24:07 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 68859 invoked by uid 500); 1 Jan 2015 09:24:07 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 68849 invoked by uid 99); 1 Jan 2015 09:24:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Jan 2015 09:24:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of riankruger@gmail.com designates 209.85.216.51 as permitted sender) Received: from [209.85.216.51] (HELO mail-qa0-f51.google.com) (209.85.216.51) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Jan 2015 09:24:02 +0000 Received: by mail-qa0-f51.google.com with SMTP id i13so9952611qae.10 for ; Thu, 01 Jan 2015 01:22:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=b7OVtgiOKTmBvdC9NsBa+v5KDmHgF2yeu27sbzhd0Ww=; b=o2rAtk8GGREN4f+PDszWiLmLifr1y47Gvj1d+TTE9KCXogvQRYfs6ILBjNslFRLHfd zE24yTmUy/CQ8IkwbyW5YV0nfEdQUWRn/UTNKm7L+Q4MfI2Ed94F+fAJFTHQijMqsC7Q yOVxLhUTcVei6IBqSH3IO1EPef9cEhzmNC3Ldthou9s59XYrsMEg1H8twnGq50whv8ov 51u+JlmAgwY2Qfxggb/1qFZK8usu9KgEqmlxfm1GgHw2YO1+KDiERWOYJmxZ7Yg2LX/p N8j4bFXp/RGyiVYC4iN+cNXsRXTJ2o7phlxbTfqYuE+q2fETV1f7Ev3i7JR22Pz0QUVD IRtg== MIME-Version: 1.0 X-Received: by 10.140.91.201 with SMTP id z67mr55129523qgd.27.1420104132285; Thu, 01 Jan 2015 01:22:12 -0800 (PST) Received: by 10.140.145.193 with HTTP; Thu, 1 Jan 2015 01:22:12 -0800 (PST) In-Reply-To: References: Date: Thu, 1 Jan 2015 11:22:12 +0200 Message-ID: From: Rian Kruger To: users Content-Type: multipart/alternative; boundary=001a113a6a4e595c76050b93c220 X-Virus-Checked: Checked by ClamAV on apache.org Subject: [users@httpd] Re: mod proxy_wstunnel invalid utf8 during upgrade --001a113a6a4e595c76050b93c220 Content-Type: text/plain; charset=UTF-8 I had to compile the latest version of apache on my server and that seemed to solve the issue. I created this question and answer to document that process: http://serverfault.com/questions/655722/how-do-i-compile-the-latest-apache2-on-ubuntu-using-the-original-layout-configu/655724#655724 On Mon, Dec 29, 2014 at 8:50 PM, Rian Kruger wrote: > Hi > > I am experiencing an intermittent problem when connecting the jetty > web-socket client to the server. The good people at Jetty assure me it is > not a problem with Jetty. > > On the server side I have apache with mod proxy_wstunnel proxying to > tomcat 7. > > When I take apache out of the picture and connect the client directly to > tomcat, the error seems to disappear. Also the error does not seem to > happen when I run the client on linux, the problem only seems to occur on > windows 7. > > I've noticed that apache is returning a 500 html page at some stage, > however, even if I set the loglevel to debug, I don't get any useful > information on how to resolve the error. > > If anyone could help me figure out how to resolve this it would be much > appreciated. Hours of googling have helped. You are my last hope... > > The software version are: > > apache Server version: Apache/2.4.7 (Ubuntu), Server built: Jul 22 2014 > 14:36:38 > tomcat Apache Tomcat/7.0.52 (Ubuntu) 1.8.0_25-b17 Oracle Corporation Linux > 3.13.0-32-generic > Jetty client: 9.2.6.v20141205 > > I've attached the logs. > > There is also a ticket on stackoverflow, should you wish to get points > there: > > > http://stackoverflow.com/questions/27638895/jetty-websocket-client-not-valid-utf8 > > Any help would be much appreciated. > > Thanks in advance. > > Rian > --001a113a6a4e595c76050b93c220 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I = had to compile the latest version of apache on my server and that seemed to= solve the issue.

I created this question and answer to document that process:

http://serverfault.com/questions/655722/how-do-= i-compile-the-latest-apache2-on-ubuntu-using-the-original-layout-configu/65= 5724#655724


On Mon, Dec 29, 2014 at 8:50 PM, Rian Kruger <= riankruger@gmail.= com> wrote:
Hi

I am experiencing an intermittent problem when conn= ecting the jetty web-socket client to the server. The good people at Jetty = assure me it is not a problem with Jetty.

On the s= erver side I have apache with mod proxy_wstunnel proxying to tomcat 7.=C2= =A0

When I take apache out of the picture and conn= ect the client directly to tomcat, the error seems to disappear. Also the e= rror does not seem to happen when I run the client on linux, the problem on= ly seems to occur on windows 7.

I've noticed t= hat apache is returning a 500 html page at some stage, however, even if I s= et the loglevel to debug, I don't get any useful information on how to = resolve the error.

If anyone could help me figure = out how to resolve this it would be much appreciated. Hours of googling hav= e helped. You are my last hope...

The software ver= sion are:

apache=C2=A0Server version: Apache/2.4.7= (Ubuntu),=C2=A0Server built: =C2=A0 Jul 22 2014 14:36:38
tomcat = Apache Tomcat/7.0.52 (Ubuntu) 1.8.0_25-b17 Oracle Corporation Linux
=C2=A0 =C2=A03.13.0-32-generic=C2=A0
Jetty client:=C2=A09.2.6.= v20141205

I've attached the logs.
There is also a ticket on stackoverflow, should you wish to ge= t points there:


Any help would be much appreciat= ed.

Thanks in advance.

Rian

--001a113a6a4e595c76050b93c220--