-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 12/5/14 11:01 AM, Chris Gamache wrote:
> Currently we use haproxy to direct users to certain versions of
> our software based on a cookie. This is so that the user can select
> which version of the software they want to use (e.g. Legacy,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Leo,
On 12/2/14 5:12 PM, Leo Donahue wrote:
> On Tue, Dec 2, 2014 at 3:28 PM, Chris Gamache
> wrote:
>
>> You could probably be more sophisticated in your throttling,
>> letting certain IPs or requests through while tarpitting others.
>>
>> I w
Yes it does without any error. I have tested 10 times with no errors
which never happened before and the value of int b does not affected
int rsv. So as far after these test I claim it is fixed in at least
7.0.53. I also filed a bug report for tomcat 7.0.53 and explained the
bug and the solution to
Currently we use haproxy to direct users to certain versions of our
software based on a cookie. This is so that the user can select which
version of the software they want to use (e.g. Legacy, Stable, Beta) ...
Having that kind of application functionality in the load balancer is
something I'd rath
Yes that was it Daniel. My browser was configured with a proxy and that
was what was causing the problem.
Sincere Thanks
Des
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h
On Fri, Dec 5, 2014 at 9:29 AM, Des Magner wrote:
> I checked the logs and the the request does not seem to be making it to
> tomcat. There is no reference to it in the access log file.
That would almost certainly indicate that something is blocking it. If the
request hit Tomcat and Tomcat wer
I checked the logs and the the request does not seem to be making it to
tomcat. There is no reference to it in the access log file. It is my own
server so blocking should not be an issue. I checked the firewall logs
and I don't see anything, But do I need to open other ports to allow
access? My
On Fri, Dec 5, 2014 at 6:21 AM, Des Magner wrote:
> Hi
>
> I cannot access any websocket applications when my client runs on a
> different machine from tomcat. It works fine if everything is on the same
> machine but once I access from a different machine I see the error below in
> my Firebug con
Hi
I cannot access any websocket applications when my client runs on a
different machine from tomcat. It works fine if everything is on the
same machine but once I access from a different machine I see the error
below in my Firebug console:
"NetworkError: 403 Forbidden -
http://remote-host:
