On Mar 22, 2013, at 4:54 PM, Stefan Fritsch s...@sfritsch.de wrote:
On Tuesday 19 March 2013, Jim Jagielski wrote:
This would be EXTREMELY easy just using -notes
But having to do a hash lookup in -notes on every read from the
network seems rather inefficient to me. I think an optional
Indeed it does and without issue.
On 2013-03-20, at 7:31 AM, Jim Jagielski wrote:
I would try the latest version on trunk. It should automatically
disable the reqtimeout filter.
On Mar 19, 2013, at 7:22 PM, Jamie Johnson jej2...@gmail.com wrote:
For those of us not familiar how would
Perfect! Thx!
On Mar 23, 2013, at 12:15 PM, Nathan Quinlan nathan.quin...@gmail.com wrote:
Indeed it does and without issue.
On 2013-03-20, at 7:31 AM, Jim Jagielski wrote:
I would try the latest version on trunk. It should automatically
disable the reqtimeout filter.
On Mar 19, 2013,
On Tuesday 19 March 2013, Jim Jagielski wrote:
This would be EXTREMELY easy just using -notes
But having to do a hash lookup in -notes on every read from the
network seems rather inefficient to me. I think an optional function
or a field in conn_rec would be better.
If we added field in
On 22 Mar 2013, at 10:54 PM, Stefan Fritsch s...@sfritsch.de wrote:
On Tuesday 19 March 2013, Jim Jagielski wrote:
This would be EXTREMELY easy just using -notes
But having to do a hash lookup in -notes on every read from the
network seems rather inefficient to me. I think an optional
I would try the latest version on trunk. It should automatically
disable the reqtimeout filter.
On Mar 19, 2013, at 7:22 PM, Jamie Johnson jej2...@gmail.com wrote:
For those of us not familiar how would this be accomplished? Is it just
config or is there also some dev that needs to happen?
On Mar 18, 2013, at 4:56 PM, Stefan Fritsch s...@sfritsch.de wrote:
Alternatively,
mod_reqtimeout could offer an API to allow modules to disable it. But
I think that is the worse of the two solutions.
Actually, I think that's the most logical solution...
This would be EXTREMELY easy just using -notes
On Mar 19, 2013, at 9:03 AM, Jim Jagielski j...@jagunet.com wrote:
On Mar 18, 2013, at 4:56 PM, Stefan Fritsch s...@sfritsch.de wrote:
Alternatively,
mod_reqtimeout could offer an API to allow modules to disable it. But
I think that is the
For those of us not familiar how would this be accomplished? Is it just
config or is there also some dev that needs to happen?
On Mar 19, 2013 9:09 AM, Jim Jagielski j...@jagunet.com wrote:
This would be EXTREMELY easy just using -notes
On Mar 19, 2013, at 9:03 AM, Jim Jagielski
On Wednesday 06 March 2013, Micha Lenk wrote:
However, using mod_websocket from the mentioned Github location, I
discovered that it has timeout issues when mod_reqtimeout is loaded
too (unless request body timeouts are disabled). Apparently
mod_reqtimeout now enforces timeouts in
Great I'm going to try that as well. Can you provide the
process...anything would be appreciated
On Mar 17, 2013 12:06 AM, Nathan Quinlan nathan.quin...@gmail.com wrote:
I was able to backport this into 2.4.4 in less than an hour. Fortunately
it isn't that different from trunk and I'm not a C
I'm sure there is documentation about how to add a module and build it as part
of the httpd compile but I basically just:
1) copied over the module into 2.4.4 src.
2) searched for mod_proxy_ajp and added the equivalent mod_proxy_wstunnel entry
in all files
3) make make install. Discovered
thanks I'll give this a try.
Is there any chance of getting this officially ported back to 2.4? I think
there are a lot of folks that would be interested in this.
On Sun, Mar 17, 2013 at 8:56 AM, Nathan Quinlan nathan.quin...@gmail.comwrote:
I'm sure there is documentation about how to add a
I was able to get this working locally as well, thanks for the steps.
On Sun, Mar 17, 2013 at 9:57 AM, Jamie Johnson jej2...@gmail.com wrote:
thanks I'll give this a try.
Is there any chance of getting this officially ported back to 2.4? I
think there are a lot of folks that would be
I was able to backport this into 2.4.4 in less than an hour. Fortunately it
isn't that different from trunk and I'm not a C guy.
On 2013-03-15, at 11:49 PM, jej2003 wrote:
Is it possible to build this module to run on an existing httpd 2.2.22
instance?
--
View this message in
From my somewhat limited testing, so far things look good...
Who can provide some more rigorous tests?
On 08.03.2013 13:40, Jim Jagielski wrote:
From my somewhat limited testing, so far things look good...
Who can provide some more rigorous tests?
I never used them myself, but http://autobahn.ws/ provides a broadly
used test suite. Mark T. uses it for his development of Websockets for
Tomcat.
Today, I think that I will actually rename it to mod_proxy_tunnel,
which is a more accurate description of the module... I expect
it will be used mostly to proxy tunnel websockets, but still,
the new name is better.
On Mar 6, 2013, at 8:51 AM, Jim Jagielski j...@jagunet.com wrote:
As trunk and
Hi Jim,
On 03/07/2013 11:45 AM CEST +02:00, Jim Jagielski wrote:
Today, I think that I will actually rename it to mod_proxy_tunnel,
which is a more accurate description of the module... I expect
it will be used mostly to proxy tunnel websockets, but still,
the new name is better.
I would
It's an http* tunnel.
On Mar 7, 2013, at 6:03 AM, Micha Lenk mi...@lenk.info wrote:
Hi Jim,
On 03/07/2013 11:45 AM CEST +02:00, Jim Jagielski wrote:
Today, I think that I will actually rename it to mod_proxy_tunnel,
which is a more accurate description of the module... I expect
it will be
Hi Jim,
On 03/07/2013 03:08 PM CEST +02:00, Jim Jagielski wrote:
It's an http* tunnel.
Yet I bet it isn't able to tunnel RPC over HTTP, as described in
Bugzilla #40029. If my humble opinion counts, please stick with
mod_proxy_websocket.
Micha
The name doesn't matter... I had already changed the name
but if people don't like it, I'm fine w/ a new name (or names)
being suggested.
On Mar 7, 2013, at 9:18 AM, Micha Lenk mi...@lenk.info wrote:
Hi Jim,
On 03/07/2013 03:08 PM CEST +02:00, Jim Jagielski wrote:
It's an http* tunnel.
Hi Jim,
On 03/06/2013 02:51 PM CEST +02:00, Jim Jagielski wrote:
As trunk and commit watchers may have noticed, I've added
a rough mod_proxy_websocket extension module to trunk. The
basic idea was to have a simple tunnel that could be used
to proxy websocket requests, and that's the design... I
Yes, from what I can see, that module is a Websockets handler and
not a proxy module, per se. I think there are some suggestions
to actually have it donated to the ASF...
Mine is simply designed to allow httpd to proxy websocket
requests, nothing else. I see the 2 as complimentary.
On Mar 6,
Hi Jim,
Am 06.03.2013 18:22, schrieb Jim Jagielski:
How does your module handle [the mod_reqtimeout] timeouts?
Still unanswered,,,
Regards,
Micha
25 matches
Mail list logo
