Re: [users@httpd] (36)File name too long

2014-09-17 Thread mmccar...@tribloom.com
gt;status = HTTP_FORBIDDEN; } On Sep 17, 2014, at 12:52 PM, Rich Bowen wrote: On 09/16/2014 02:50 PM, mmccar...@tribloom.com wrote: I am using RewriteRule and the proxy flag to proxy through Apache. When a long URL is passed through (longer than 255 characters), I get the erro

[users@httpd] (36)File name too long

2014-09-16 Thread mmccar...@tribloom.com
I am using RewriteRule and the proxy flag to proxy through Apache. When a long URL is passed through (longer than 255 characters), I get the error below (redacted). I understand that this is related to the maximum file name on the OS, in this case Ubuntu 14.04. My question is why is this happen

Re: [users@httpd] How to Proxy and Rewrite URLs and responses with multiple instances to replace in URL

2014-09-15 Thread mmccar...@tribloom.com
nks, Michael On 9/15/2014 10:07 AM, mmccar...@tribloom.com wrote: Hello. I have been attempting to restrict access to Kibana/ElasticSearch using Apache 2.4. Kibana, ElasticSearch, and Apache are all on the same server. Kibana is on port 9292, ElasticSearch is on port 9200, Apache is on 80. My

[users@httpd] How to Proxy and Rewrite URLs and responses with multiple instances to replace in URL

2014-09-15 Thread mmccar...@tribloom.com
Hello. I have been attempting to restrict access to Kibana/ElasticSearch using Apache 2.4. Kibana, ElasticSearch, and Apache are all on the same server. Kibana is on port 9292, ElasticSearch is on port 9200, Apache is on 80. My approach has been to proxy request through Apache and rewrite UR