Re: [users@httpd] virtual host configuration
On 07/23/2015 03:48 PM, Mathijs Schmittmann wrote: K R schreef op 7/23/2015 om 9:44 PM: Hi, my customer want to configure virtual host for 5 website in one apache environment . do i have to get 5 ip addresses from network team. Can someone please point me on how can i achieve the same No, you should create 5 virtualhosts in your configuration and let the Apache HTTPD listen on 1 IP. Based on which website is requested (technically based on the 'Host' header in the HTTP request) the httpd will select the right DocumentRoot for serving a response. For more information about virtualhosts: http://wiki.apache.org/httpd/ExampleVhosts http://httpd.apache.org/docs/current/vhosts/examples.html Thanks in advance Best regards, Mathijs Schmittmann This is called name-based virtual hosting if you want to run a web search for it. That may yield some help for you also. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] php-fpm and proxy , httpd 2.4.12
On Thu, Jul 23, 2015 at 3:15 PM, MM finjulh...@gmail.com wrote: You need to choose mod_php or fpm. Don't load both. I personally usually use mod_php. Is it that with mod_php, httpd runs php in process while fpm delegates to separate processes? Correct. - Y
Re: [users@httpd] SSL Session Id lost?
On Thu, Jul 23, 2015 at 3:50 PM, Alex Soto asot...@gmail.com wrote:
It seems that everything is configured correctly since sometimes works. Have
you ever found something similar or knows what it can be happening? Do you
think that maybe the problem is on client (browser) side?
We say that there is something in Apache Httpd since I have modified what
was printed in access_log file to print the ssl session id as second
parameter. And I get next:
(LogFormat %H %{SSL_SESSION_ID}e %h %l %u %t \%r\ %s %b)
HTTP/1.1 - 172.17.42.1 - - [09/Jul/2015:09:15:06 +] GET /hello/hello
HTTP/1.1 200 89
This is because the SSL_SESSION_ID is not always available on the TLS
side, when session tickets are used at first.
It's up to the client to generate (or not) a session ID, which is only
available on the first session resumption.
https://tools.ietf.org/html/rfc5077#section-3.4 for the details.
You may configure SSLSessionTickets off to disable session tickets
management in TLS (using session IDs only).
Regards,
Yann.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Request Entity Too Large
Hi everyone, We are suddenly having the following problem on several of our servers, and I have not been able to find a solution on the internet that has resolved it. Our configuration is the following. Apache httpd 2.2.3 running on RHEL5 Tomcat 7, also running on RHEL5 When we try to upload a file bigger than a few megabytes, we get the following error: The requested resource /dse/submissions/100103040/add_file does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit I've tried to figure out what the maximum size file is, but the problem will occur on a file, and then we try the same file a few minutes later and it works. I tried setting LimitRequestBody to 0, which I believe is the default anyway, but it had no effect either way. If anyone has any ideas, please let me know. Thanks, Larry Cohen
[users@httpd] Re: Request Entity Too Large
Forgot to mention. The httpd error code is 413. Thanks, Larry Cohen On Thu, Jul 23, 2015 at 5:04 PM, Cohen, Laurence lco...@novetta.com wrote: Hi everyone, We are suddenly having the following problem on several of our servers, and I have not been able to find a solution on the internet that has resolved it. Our configuration is the following. Apache httpd 2.2.3 running on RHEL5 Tomcat 7, also running on RHEL5 When we try to upload a file bigger than a few megabytes, we get the following error: The requested resource /dse/submissions/100103040/add_file does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit I've tried to figure out what the maximum size file is, but the problem will occur on a file, and then we try the same file a few minutes later and it works. I tried setting LimitRequestBody to 0, which I believe is the default anyway, but it had no effect either way. If anyone has any ideas, please let me know. Thanks, Larry Cohen -- [image: www.novetta.com] Larry Cohen System Administrator 12021 Sunset Hills Road, Suite 400 Reston, VA 20190 Email lco...@novetta.com Office 703-885-1064
Re: [users@httpd] Apache Performance Question
Hi, There is a limit on the number of concurrent connections that Apache will serve. See if you can find the 'LogLevel' directive in your configuration and then set it to 'info'. Apache will then print warnings in your error log if you're reaching those limits. http://httpd.apache.org/docs/2.2/mod/core.html#loglevel You can also use the /server-status page to check this:- http://httpd.apache.org/docs/2.2/mod/mod_status.html or for a rough point-in-time estimate you can simply use 'netstat' to see how many established connections you have to your HTTP port (probably port 80). The command:- netstat -tan | grep ':80' | grep EST | wc -l is quite possibly what you need depending on your OS and Apache version which will count the established connections to port 80 on Linux. If you do need to increase the number of concurrent connections, you will probably need to raise MaxClients and ServerLimit. See - http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients Hope that helps. Phil. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Directory matching when Location should match
Hello!
I have a configuration (apache 2.2, soon 2.4) which basically is
VirtualHost 10.1.2.3:80
DocumentRoot /var/www
Location /server-status
SetHandler server-status
/Location
Directory /var/www/
RewriteEngine On
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI}
/Directory
/VirtualHost
(of course there is another VirtualHost on port 443)
I want to redirect all requests for _filesystem_ objects to a secure
connection, but the non-filesystem object served via a handler should
be available unencrypted. (FYI: I use the server-status for health
check by a loadbalancer, but the documents are protected by shibboleth)
However, also requests for /server-status get redirected :( Documentation
says Enclose a group of directives that apply only to the named file-system
directory, sub-directories, and their contents. Cleary /server-status is
not within /var/www ...
My naive imagination would be that apache performs a url-to-filesystem-
path conversion, and only if the outcome really is a directory or a file,
then applies the corresponding directives. Either this is not the case,
or I'm missing something completly :(
There is a hidden hint in the docs for RewriteCond:
REQUEST_FILENAME The full local filesystem path to the file or script
matching the request, if this has already been determined by the server
at the time REQUEST_FILENAME is referenced. Otherwise, such as when used
in virtual host context, the same value as REQUEST_URI. Depending on the
value of AcceptPathInfo, the server may have only used some leading
components of the REQUEST_URI to map the request to a file.
After reading this, I tried
RewriteCond %{LA-U:REQUEST_FILENAME} /var/www/.*
with no effect :(
Is there anybody familiar enough with how apache's working to explain
what's happening here? Or better yet, does somebody have any idea how
to accomplish what I'm seeking to do, i.e. redirecting all filesystem
objects while leaving alone all virtual URLs?
TIA, Andy
--
Andreas Ley, SCC, Karlsruhe Institute of Technology (KIT), D-76128 Karlsruhe
E-Mail: andreas@kit.edu, Telephone: +49 721 608 46341, Fax: +49 721 32550
From the home of the imaginary deadlines:
It will take 2i weeks to do that project. -- Michael Sinz
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Apache Performance Question
In the past on our 2.2 configs we used prefork with mod_php To set our MaxClients we determine an average amount of RAM used by httpd processes by looking at top output, we then divide the (total amount of physical RAM minus enough RAM to run the OS) by the average RAM used by httpd processes. In 2.4 we are using event MPM with PHP-FPM. So for MaxRequestWorkers we get the average RAM per httpd process like above plus the average RAM per PHP-FPM process then divide the physical RAM by that. I am not clear on how to determine the other 2.4 event MPM config settings (MaxConnectionsPerChild, etc.). There doesn't seem to be much reference to event specific settings and how to arrive at values here, http://httpd.apache.org/docs/2.4/mod/mpm_common.html If you have a lot of RAM and not a proportional amount of cpu then to me your cpu is the constraint. On 7/23/15 8:14 AM, Philip Wigg p...@philipwigg.co.uk wrote: Hi, There is a limit on the number of concurrent connections that Apache will serve. See if you can find the 'LogLevel' directive in your configuration and then set it to 'info'. Apache will then print warnings in your error log if you're reaching those limits. http://httpd.apache.org/docs/2.2/mod/core.html#loglevel You can also use the /server-status page to check this:- http://httpd.apache.org/docs/2.2/mod/mod_status.html or for a rough point-in-time estimate you can simply use 'netstat' to see how many established connections you have to your HTTP port (probably port 80). The command:- netstat -tan | grep ':80' | grep EST | wc -l is quite possibly what you need depending on your OS and Apache version which will count the established connections to port 80 on Linux. If you do need to increase the number of concurrent connections, you will probably need to raise MaxClients and ServerLimit. See - http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients Hope that helps. Phil. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Apache 2.4: SSLProtocol directive not taking effect
Hi, You may be hitting bug [1], which has been fixed in latest 2.4.16 and 2.2.31. Not sure anymore that the bug indicated is the one affecting our Apache installation. Seems like the SSLCipherSuite directive is also simply ignored. This is very peculiar, since any and all directives in a VirtualHost context is active, except for the ones pertaining to SSL. What could be a common cause of such behaviour? We just don't know what to do... Regards, François
Re: [users@httpd] Fwd: SSI directives not working on page used in ErrorDocument directive
What mechanism are you using to have SSI work on .html pages? I have no problem getting SSI to work when my page extension is .shtml: This is my very simple test which works perfectly: .htaccess: Options +Includes ErrorDocument 404 /error.shtml error.shtml: Last modified: !--#echo var=LAST_MODIFIED -- Produces: Last modified: Thursday, 23-Jul-2015 23:34:55 Eastern Daylight Time Does it work for you if you use .shtml? - Y On Thu, Jul 23, 2015 at 4:06 PM, eigenbra...@gmail.com wrote: Forgot to include my question, Is there some additional step you have to take to get SSI to function on an ErrorDocument page? Thanks - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Fwd: SSI directives not working on page used in ErrorDocument directive
I have Apache configured to parse all html files for SSI directives. I did try re-naming it to .shtml just to make sure though and it still does not fire the SSI directives, I even removed all but the example you have there but it still doesn't function. Still works when hitting directly, but not when used int he ErrorDocument. The only difference i have is I'm using Options IncludesNOEXEC But I'm not using any exec directives so that shouldn't be the issue could it? On Thu, Jul 23, 2015 at 10:36 PM, Yehuda Katz yeh...@ymkatz.net wrote: What mechanism are you using to have SSI work on .html pages? I have no problem getting SSI to work when my page extension is .shtml: This is my very simple test which works perfectly: .htaccess: Options +Includes ErrorDocument 404 /error.shtml error.shtml: Last modified: !--#echo var=LAST_MODIFIED -- Produces: Last modified: Thursday, 23-Jul-2015 23:34:55 Eastern Daylight Time Does it work for you if you use .shtml? - Y On Thu, Jul 23, 2015 at 4:06 PM, eigenbra...@gmail.com wrote: Forgot to include my question, Is there some additional step you have to take to get SSI to function on an ErrorDocument page? Thanks - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] virtual host configuration
Hi, my customer want to configure virtual host for 5 website in one apache environment . do i have to get 5 ip addresses from network team. Can someone please point me on how can i achieve the same Thanks in advance
Re: [users@httpd] virtual host configuration
K R schreef op 7/23/2015 om 9:44 PM: Hi, my customer want to configure virtual host for 5 website in one apache environment . do i have to get 5 ip addresses from network team. Can someone please point me on how can i achieve the same No, you should create 5 virtualhosts in your configuration and let the Apache HTTPD listen on 1 IP. Based on which website is requested (technically based on the 'Host' header in the HTTP request) the httpd will select the right DocumentRoot for serving a response. For more information about virtualhosts: http://wiki.apache.org/httpd/ExampleVhosts http://httpd.apache.org/docs/current/vhosts/examples.html Thanks in advance Best regards, Mathijs Schmittmann - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Fwd: SSI directives not working on page used in ErrorDocument directive
Forgot to include my question, Is there some additional step you have to take to get SSI to function on an ErrorDocument page? Thanks - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Request Entity Too Large
Ok, thank you. On Thu, Jul 23, 2015 at 5:18 PM, Yehuda Katz yeh...@ymkatz.net wrote: The first thing to check is if it is an HTTPD error or a Tomcat error. You haven't explicitly said this, but I am guessing you are using HTTPD as a reverse proxy. Check the Tomcat logs first. If the 413 shows up there, it is a problem with Tomcat and not with HTTPD. Check the HTTPD error log also to make sure the errors are actually in it. It is also possible if there are any upstream proxies (like an office web filter) that one of them is generating the error. If the error is in the HTTPD logs and not in the Tomcat logs, you will probably need to dump the traffic using mod_dumpio or tcpdump and compare a complete and error request (mod_logio will tell you the sizes, but not the contents - you could use it as a starting point if you don't want to dump all the traffic). - Y On Thu, Jul 23, 2015 at 5:04 PM, Cohen, Laurence lco...@novetta.com wrote: Hi everyone, We are suddenly having the following problem on several of our servers, and I have not been able to find a solution on the internet that has resolved it. Our configuration is the following. Apache httpd 2.2.3 running on RHEL5 Tomcat 7, also running on RHEL5 When we try to upload a file bigger than a few megabytes, we get the following error: The requested resource /dse/submissions/100103040/add_file does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit I've tried to figure out what the maximum size file is, but the problem will occur on a file, and then we try the same file a few minutes later and it works. I tried setting LimitRequestBody to 0, which I believe is the default anyway, but it had no effect either way. If anyone has any ideas, please let me know. Thanks, Larry Cohen -- [image: www.novetta.com] Larry Cohen System Administrator 12021 Sunset Hills Road, Suite 400 Reston, VA 20190 Email lco...@novetta.com Office 703-885-1064
Re: [users@httpd] Request Entity Too Large
The first thing to check is if it is an HTTPD error or a Tomcat error. You haven't explicitly said this, but I am guessing you are using HTTPD as a reverse proxy. Check the Tomcat logs first. If the 413 shows up there, it is a problem with Tomcat and not with HTTPD. Check the HTTPD error log also to make sure the errors are actually in it. It is also possible if there are any upstream proxies (like an office web filter) that one of them is generating the error. If the error is in the HTTPD logs and not in the Tomcat logs, you will probably need to dump the traffic using mod_dumpio or tcpdump and compare a complete and error request (mod_logio will tell you the sizes, but not the contents - you could use it as a starting point if you don't want to dump all the traffic). - Y On Thu, Jul 23, 2015 at 5:04 PM, Cohen, Laurence lco...@novetta.com wrote: Hi everyone, We are suddenly having the following problem on several of our servers, and I have not been able to find a solution on the internet that has resolved it. Our configuration is the following. Apache httpd 2.2.3 running on RHEL5 Tomcat 7, also running on RHEL5 When we try to upload a file bigger than a few megabytes, we get the following error: The requested resource /dse/submissions/100103040/add_file does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit I've tried to figure out what the maximum size file is, but the problem will occur on a file, and then we try the same file a few minutes later and it works. I tried setting LimitRequestBody to 0, which I believe is the default anyway, but it had no effect either way. If anyone has any ideas, please let me know. Thanks, Larry Cohen
Re: [users@httpd] Directory matching when Location should match
On Thu, Jul 23, 2015 at 9:45 AM, Andreas Ley andreas@kit.edu wrote: However, also requests for /server-status get redirected :( Documentation says Enclose a group of directives that apply only to the named file-system directory, sub-directories, and their contents. Cleary /server-status is not within /var/www ... Your issue is partially due to how mod_status is configured only via SetHandler. Nothing actually stops other phases of Apache processing from mapping /server-status to $docroot/server-status, it's just that the module that serves static files [separate from how URLs are mapped to the filesystem) is pre-empted by mod_status. Something like mod_proxy OTOH, would have short-circuited that URL to filesystem mapping. -- Eric Covener cove...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] SSL Session Id lost?
Hello I have seen a strange behaviour in Apache HTTPD (2.4) and TomEE (in
fact it is a Tomcat (7.0.61) so it is exactly the same for Tomcat) when I
configure Apache server with SSL and mod_jk. I have been asking in the
Tomcat/mod_jk mailing list and after several discussion it seems that there
is something strange (may be it is correct of course but we don't
understand why) in Apache HTTPD side.
I am configuring the typical Apache as frontend and TomEE(Tomcat) as
backend solution. Currently Apache is configured with SSL and with mod_jk
it connects to TomEE using AJP. This works perfectly. The problem is that
inside my code I need to get the ssl session id:
String ssl =
(String)servletRequest.getAttribute(javax.servlet.request.ssl_session_id);
I don't know why but sometimes this attribute is null and sometimes not. It
may return a null at first requests then stay like 10 requests working and
then stop working again during some requests and the get attribute returns
null.
It seems that everything is configured correctly since sometimes works.
Have you ever found something similar or knows what it can be happening? Do
you think that maybe the problem is on client (browser) side?
We say that there is something in Apache Httpd since I have modified what
was printed in access_log file to print the ssl session id as second
parameter. And I get next:
(LogFormat %H %{SSL_SESSION_ID}e %h %l %u %t \%r\ %s %b)
HTTP/1.1 - 172.17.42.1 - - [09/Jul/2015:09:15:06 +] GET /hello/hello
HTTP/1.1 200 89
HTTP/1.1 1b17f16f8ae73c1b4d706c1598aadb596db610bbdaeb1cd967e0bea98ec2abcb
172.17.42.1 - - [09/Jul/2015:09:15:34 +] GET /hello/hello HTTP/1.1
200 209
Notice that the first request does not contain the SSL SESSION ID although
of course I have accessed using https protocol. Then after several retries
(basically refreshing the browser) the ssl session id appear in the log and
of course then it can be retrieved in Java part. So it seems that there is
something related in httpd (maybe there is an explanation) to know why at
first queries httpd doesn't set ssl session id and after some time it
starts to do it.
Everything is dockerized here:
https://github.com/lordofthejars/apache-tomee-ssl so you can review
configuration files of tomcat and httpd or even run it. You can read if you
want all the discussion in Tomcat mailing list in
http://mail-archives.apache.org/mod_mbox/tomcat-users/201507.mbox/browser
Thank you so much for your support.
Re: [users@httpd] Apache Performance Question
Thank you for the reply John. I'm using Apache 2.2 and I'm novice, would you mind providing some detailed steps to figure out what the issue is? If my initial explanation is vague, what other info do you need if any? Much appreciated On Jul 23, 2015 6:30 AM, Rose, John B jbr...@utk.edu wrote: In the past on our 2.2 configs we used prefork with mod_php To set our MaxClients we determine an average amount of RAM used by httpd processes by looking at top output, we then divide the (total amount of physical RAM minus enough RAM to run the OS) by the average RAM used by httpd processes. In 2.4 we are using event MPM with PHP-FPM. So for MaxRequestWorkers we get the average RAM per httpd process like above plus the average RAM per PHP-FPM process then divide the physical RAM by that. I am not clear on how to determine the other 2.4 event MPM config settings (MaxConnectionsPerChild, etc.). There doesn't seem to be much reference to event specific settings and how to arrive at values here, http://httpd.apache.org/docs/2.4/mod/mpm_common.html If you have a lot of RAM and not a proportional amount of cpu then to me your cpu is the constraint. On 7/23/15 8:14 AM, Philip Wigg p...@philipwigg.co.uk wrote: Hi, There is a limit on the number of concurrent connections that Apache will serve. See if you can find the 'LogLevel' directive in your configuration and then set it to 'info'. Apache will then print warnings in your error log if you're reaching those limits. http://httpd.apache.org/docs/2.2/mod/core.html#loglevel You can also use the /server-status page to check this:- http://httpd.apache.org/docs/2.2/mod/mod_status.html or for a rough point-in-time estimate you can simply use 'netstat' to see how many established connections you have to your HTTP port (probably port 80). The command:- netstat -tan | grep ':80' | grep EST | wc -l is quite possibly what you need depending on your OS and Apache version which will count the established connections to port 80 on Linux. If you do need to increase the number of concurrent connections, you will probably need to raise MaxClients and ServerLimit. See - http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients Hope that helps. Phil. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] php-fpm and proxy , httpd 2.4.12
On 22 July 2015 at 20:49, Yehuda Katz yeh...@ymkatz.net wrote: Do you need this configuration to be portable to different systems with different modules available? No If not, remove all the IfModule directives and only include the configuration that you really want to use. All right... This will make sure that you understand what your server is doing and will make sure you get the correct errors about what is missing. You need to choose mod_php or fpm. Don't load both. I personally usually use mod_php. Is it that with mod_php, httpd runs php in process while fpm delegates to separate processes? If you are using FPM, You need to verify that the php-fpm socket is really there and that FPM configuration is correct for your environment. You can also enable mod_info to see what modules are actually loaded and what configuration is being skipped. - Y Thanks
[users@httpd] SSI directives not working on page used in ErrorDocument directive
Firstly SSI directives are working on my server. If i access the file directly everything functions as expected. Working example file path explanation - 1. Enter in browser: http://example.com/apps/pagenotfound/index.html 2. This is a symlink to: /temp/comp/apps/applayer/index.html The issue arises when I plug the 404 page into my Error Document as follows: ErrorDocument 404 /apps/pagenotfound/index.html If I then type in a trash page it calls the custom 404 page correctly but none of the SSI directives seem function. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Re: Http trailers in chunked requests
On Thu, Jul 23, 2015 at 11:03 AM, Sachin Shetty sachin.she...@gmail.com wrote: From the change list, I found that you added support for MergeTrailers in 2.4.11 - any idea on how I could make it work? I just need apache to let the trailers pass through to the upstream haproxy, I am not processing them in mod headers or other apache modules. MergeTrailers on will not put the client's trailers into the ones to be sent to the backend (as you may expect), but instead it merges them into client's headers (obviously after those have already been sent to the backend...). This directive aims to preserve the previous behaviour of httpd (which was wrong, but we wanted anyone broken by the change to be able to recover). The new default is to discard the trailers (or more exactly to put them separately in the request/response trailers table, but nothing is using it for now). I think you should request an enhancement on the bugzilla for mod_proxy (at least) to handle/forward the trailers, that's not the case currently, and I agree this is the sequel. Please note that the trailers shall not be handled/forwarded blindly, the RFC 7230 (sections 4.1.2, 4.3 and 4.4) is quite strict about acceptable trailers and how they ought to be announced in the headers (TE, Trailer, ...), so clients have to conform too. Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Re: Http trailers in chunked requests
Hi Eric, Sorry to be bugging you on this one, I grepped through the source and I see some solid references to trailer processing. From the change list, I found that you added support for MergeTrailers in 2.4.11 - any idea on how I could make it work? I just need apache to let the trailers pass through to the upstream haproxy, I am not processing them in mod headers or other apache modules. Thanks Sachin On Wed, Jul 22, 2015 at 4:55 PM, Sachin Shetty sachin.she...@gmail.com wrote: Hi, I tried with Apache 2.4.16 with the MergeTrailers On. No luck, apache just wont let the trailers pass through. I enabled debug log as well, but no additional info in logs about skipping trailers. Thanks Sachin On Mon, Jul 20, 2015 at 11:44 AM, Sachin Shetty sachin.she...@gmail.com wrote: Hi Eric, We are using mod proxy and mod rewrite to forward the request to an haproxy server running a pool of tomcat. I have verified that when the request is directly sent to haproxy, trailers are sent to the tomcat and it does print it in the debug logs. While debugging this I have also noticed that apache converts a chunked request 8KB to a non chunked one and assembled the whole body before sending it down the proxy. Thanks Sachin Sorry could not figure out how to post from a digest, I have copied your question below: What module handles this request, and where are you looking for the trailers? On Sat, Jul 18, 2015 at 6:27 PM, Sachin Shetty sachin.she...@gmail.com wrote: Hi, as per http spec, we want clients to send us trailers in chunked requests. However the request on the server side does not get the trailer at all. Is there some setting on apache to allow trailers, we are using apache 2.4. Our request looks like this. telnet somehost 80 POST /some-path HTTP/1.1 Authorization: Basic = Host: somehost.domain.com Transfer-Encoding: chunked Trailer: My-Test-Trailer 50 0 My-Test-Trailer: some-value-new -- Thanks Regards Sachin Shetty I never make mistakeas
