Re: [users@httpd] Why ExpiresByType is ignored when has SetHandler application/x-httpd-php ?

Oh I should add - when it is a php file I also set the cache control via php. header('Cache-Control: max-age=' . $maxage); for example. On 12/27/2016 11:12 PM, Michael A. Peters wrote: Hi, I regularly use php to generate all kinds of different XML. This is what I do - header('Content-Type:

Re: [users@httpd] Why ExpiresByType is ignored when has SetHandler application/x-httpd-php ?

Hi, I regularly use php to generate all kinds of different XML. This is what I do - header('Content-Type: application/xml'); print($dom->saveXML()); exit(); Of course in that case $dom is a DOMDocument object - if you are using print or echo to create XML then you need the header at the

Re: [users@httpd] Why ExpiresByType is ignored when has SetHandler application/x-httpd-php ?

בע"ה Hi, As I wrote in earlier example, `Header set Content-Type "application/xml"` still returns 1 day expiration (not the one defined in ExpiresByType). The same result when switching configuration order of FilesMatch before ExpiresDefault, or order of LoadModule's expires_module and

Re: [users@httpd] Why ExpiresByType is ignored when has SetHandler application/x-httpd-php ?

It might have something to do with the order the modules handle the request. What happens if you tell PHP to set the content type to application/xml? - Y On Tue, Dec 27, 2016 at 3:55 PM, Binyamin <7rai...@inbox.lv> wrote: > בע"ה > > > Why ExpiresByType is ignored when has SetHandler

[users@httpd] Why ExpiresByType is ignored when has SetHandler application/x-httpd-php ?

בע"ה Why ExpiresByType is ignored when has SetHandler application/x-httpd-php ? /sitemap.xml Response Headers shows 1 day expiration while expected to be 1 year (1 month) Content-Type: application/xml; charset=utf-8 Date: Tue, 27 Dec 2016 19:59:00 GMT Expires: Wed, 28

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

Perhaps something useful - I do see that the "serveradmin" command says that it runs apache 2.2 even though "httpd -v" says 2.4.23?? httpd -v Server version: Apache/2.4.23 (Unix) Server built: Aug 8 2016 16:31:34 sudo serveradmin fullstatus web web:health = _empty_dictionary

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

I have upgraded to MacOS 10.12 so now Apache 2.4.23 is the current version. Either way the patch that was suggested was supposed to have been included in 2.4.10. 2016-12-27 11:29 GMT-03:00 Adam Teale : > Otis do you know if it pretty straightforward to apply a patch to an >

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

You can also check this URL: http://blog.revathskumar.com/2015/09/proxy-websocket-via-apache.html Thanks, Otis On Tue, Dec 27, 2016 at 9:07 AM, Adam Teale wrote: > ​Hi Daniel, > > Yes in the http_server_app.conf file it is activated: > LoadModule ssl_module

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

Check this link out. http://stackoverflow.com/questions/17889676/apache-2-4-6-reverseproxy-mod-proxy-wstunnel-for-secure-websocket-wss-fails Thanks, Otis On Tue, Dec 27, 2016 at 8:55 AM, Daniel wrote: > Silly question perhaps, are you also loading mod_ssl? > > 2016-12-27

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

​Hi Daniel, Yes in the http_server_app.conf file it is activated: LoadModule ssl_module libexec/apache2/mod_ssl.so It is interesting though that when I run an "sudo apachectl -M" i can't see ssl_module in there. ​

Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

Silly question perhaps, are you also loading mod_ssl? 2016-12-27 14:39 GMT+01:00 Adam Teale : > Hi! > > I've been trying to setup a reverse proxy to a localhost websocket url. > > ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/ > ProxyPassReverse /chat/stream/

[users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL

Hi! I've been trying to setup a reverse proxy to a localhost websocket url. ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/ ProxyPassReverse /chat/stream/ wss://localhost:8000/chat/stream/ I get an error in the apache error_log that reads: No protocol handler was valid for the URL

Re: [users@httpd] httpd-2.4.25 compile fail

maybe, have a look on how Arnaud Icard solved his compilation problem on a Mac (october 18 2015) http://httpd.markmail.org/search/?q=aterrestris#query:aterrestris+page:1+mid:jp2j7dr4kkwrokz7+state:results 2016-12-27 10:34 GMT+01:00 Daniel : > Afaik httpd 2.4 is not yet

Re: [users@httpd] httpd-2.4.25 compile fail

Afaik httpd 2.4 is not yet compatible with openssl 1.1.x, the max version you can use is 1.0.2x. 2016-12-27 1:24 GMT+01:00 Kent Frazier : > I'm trying (unsuccessfully) to build on a Mac Pro version 10.12.2 > (Sierra Darwin Kernel Version 16.3.0) > > libtool (GNU