You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by André Warnier <aw...@ice-sa.com> on 2015/07/01 12:42:52 UTC
Re: why is Tomcat 7 invoking WebSocket protocol?
Caldarale, Charles R wrote:
>> From: André Warnier [mailto:aw@ice-sa.com]
>> Subject: Re: why is Tomcat 7 invoking WebSocket protocol?
>
>> But maybe the solution consists simply in renaming that filter, so that it does not
>> give the mistaken impression that the WebSocket protocol is necessarily being used ?
>
> That can't be a "solution", because there really isn't a problem here. The WsFilter has to be in the chain, just in case there's a websocket upgrade in the request. The OP needs to focus on the real problem, not this non-issue.
>
Hi.
I did not mean "solution" as correcting a "problem". I understand that the filter has to
be there.
I meant "solution" in the sense of probably avoiding a lot of questions in the future
about the same thing. Maybe renaming it to something like "ProtocolDetectionFilter" would
be less of a trigger for the uninformed public.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: why is Tomcat 7 invoking WebSocket protocol?
Posted by Ric Bernat <ri...@brinydeep.net>.
On 7/1/2015 5:44 AM, Konstantin Kolinko wrote:
> 2015-07-01 13:42 GMT+03:00 André Warnier <aw...@ice-sa.com>:
>> Caldarale, Charles R wrote:
>>>> From: André Warnier [mailto:aw@ice-sa.com] Subject: Re: why is Tomcat 7
>>>> invoking WebSocket protocol?
>>>
>>>> But maybe the solution consists simply in renaming that filter, so that
>>>> it does not give the mistaken impression that the WebSocket protocol is
>>>> necessarily being used ?
>>>
>>> That can't be a "solution", because there really isn't a problem here.
>>> The WsFilter has to be in the chain, just in case there's a websocket
>>> upgrade in the request. The OP needs to focus on the real problem, not this
>>> non-issue.
>>>
>> Hi.
>> I did not mean "solution" as correcting a "problem". I understand that the
>> filter has to be there.
>> I meant "solution" in the sense of probably avoiding a lot of questions in
>> the future about the same thing. Maybe renaming it to something like
>> "ProtocolDetectionFilter" would be less of a trigger for the uninformed
>> public.
>
> Explanation why WsFilter is needed is here:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=55855
>
> Maybe it is worth mentioning the filter in
> http://tomcat.apache.org/tomcat-8.0-doc/config/filter.html I do not
> think that it is worth renaming it.
>
> I added mention of configuration option to
> https://wiki.apache.org/tomcat/HowTo/FasterStartUp
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Hi. I am the OP. Thanks, all, for this discussion. I see that I was
barking up the wrong tree with my WebSocket theory. I have confirmed
that our problem exists outside of the (apparent) WebSocket processing.
Sorry to jump to an incorrect conclusion. We will track down our
problem, and I will reply back here if there is anything useful and/or
Tomcat-related to report.
Ric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: why is Tomcat 7 invoking WebSocket protocol?
Posted by Konstantin Kolinko <kn...@gmail.com>.
2015-07-01 13:42 GMT+03:00 André Warnier <aw...@ice-sa.com>:
> Caldarale, Charles R wrote:
>>>
>>> From: André Warnier [mailto:aw@ice-sa.com] Subject: Re: why is Tomcat 7
>>> invoking WebSocket protocol?
>>
>>
>>> But maybe the solution consists simply in renaming that filter, so that
>>> it does not give the mistaken impression that the WebSocket protocol is
>>> necessarily being used ?
>>
>>
>> That can't be a "solution", because there really isn't a problem here.
>> The WsFilter has to be in the chain, just in case there's a websocket
>> upgrade in the request. The OP needs to focus on the real problem, not this
>> non-issue.
>>
> Hi.
> I did not mean "solution" as correcting a "problem". I understand that the
> filter has to be there.
> I meant "solution" in the sense of probably avoiding a lot of questions in
> the future about the same thing. Maybe renaming it to something like
> "ProtocolDetectionFilter" would be less of a trigger for the uninformed
> public.
Explanation why WsFilter is needed is here:
https://bz.apache.org/bugzilla/show_bug.cgi?id=55855
Maybe it is worth mentioning the filter in
http://tomcat.apache.org/tomcat-8.0-doc/config/filter.html I do not
think that it is worth renaming it.
I added mention of configuration option to
https://wiki.apache.org/tomcat/HowTo/FasterStartUp
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org