Hi,
On Mon, Mar 4, 2013 at 7:22 PM, ylavic dev ylavic@gmail.com wrote:
I've been working on a patch for mod_cache to deal (fully) with the
response header Cache-Control and the no-cache=header or private=header
directives.
I realize that, maybe, the patch should have been included in the
On 06 Mar 2013, at 12:04 PM, Yann Ylavic ylavic@gmail.com wrote:
I've been working on a patch for mod_cache to deal (fully) with the
response header Cache-Control and the no-cache=header or private=header
directives.
I realize that, maybe, the patch should have been included in the
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 still
need to add the basic 'send initial rec'd headers' to the
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
Hi,
I have a C++ shared library with a lot of utile things and I built my
module against it.
I copied it into bin then in module folder but even so the server does not
find it.
What I am missing here?
The error is:
/home/xyz/indian/conf/httpd.conf: Cannot load modules/mod_xyz.so into
server:
A custom handler which is registered to run first(APR_HOOK_FIRST) has these
fields null when processing http request:
r-content_type, r-parsed_uri.scheme
the http request on the wire has the content_type header set.
r-parsed_uri.path is not null though.
apache is configured as reverse
On Wed, Mar 6, 2013 at 4:21 PM, Nce Rt nce...@yahoo.com wrote:
A custom handler which is registered to run APR_HOOK_FIRST has these fields
null when processing http request:
r-content_type, r-parsed_uri.scheme
r-content_type is not related to any request header -- it's the
response
A custom handler which is registered to run first(APR_HOOK_FIRST) has these
fields null when processing http request:
r-content_type, r-parsed_uri.scheme wherer is a pointer to request_rec
the http request on the wire has the content_type header set.
r-parsed_uri.path is not null
It's request_rec which represents http Request not Response. look into this
data structure for the content-type field.
From: Eric Covener cove...@gmail.com
To: modules-dev@httpd.apache.org; Nce Rt nce...@yahoo.com
Sent: Wednesday, March 6, 2013 2:50 PM
On Wed, Mar 6, 2013 at 6:34 PM, Nce Rt nce...@yahoo.com wrote:
It's request_rec which represents http Request not Response. look into this
data structure for the content-type field.
That's not how the field is used. If you want to read a Content-Type
request header, read it from r-headers_in.
Probably not, because you will have to cater to the MPM - e.g. use shared
memory if a subsequent request comes into a different process.
I'd suggest using shared memory (there are apr routines to do that), and
that should guarantee that state will be shared between different threads
or processes.
13 matches
Mail list logo