Yann,

Thanks for helping!

About CGI modules, the only module we are loading is "cgi_module modules / 
mod_cgi.so". We are not loading mod_proxy_fcgi / mod_fcgi.

One information I forgot to mention in the first email is:

When we are in non-secure mode, via port 8086, on localhost or on the same 
network the content is not cut and CGI reads all content.

When we are out of the network where the APACHE server is running, through port 
8086 in non-secure mode, the content is cut off and the CGI only reads the 
first 8000 bytes.

So we can not read all the content when we are remote and not secure, without 
SSL.

I did not get the network trace between httpd and the backend because I did not 
know the wireshark, I'll try this.

Ramon

-----Mensagem original-----
De: Yann Ylavic [mailto:[email protected]] 
Enviada em: terça-feira, 7 de novembro de 2017 11:04
Para: [email protected]
Assunto: Re: [users@httpd] Receiving only 8000 bytes in CGI programs using post 
method

Hi,

On Tue, Nov 7, 2017 at 12:27 PM, Ramon Loureiro <[email protected]> wrote:
>
> Here is the brief description of the problem we are in.

Which cgi module is used on httpd? mod_proxy_fcgi, mod_fcgi?

>
> When we use the Apache server to service non-secure web pages (server 
> running on port 8086) all bytes are sent to CGI programs during the 
> publishing method. Always returns response 200, and does not return 
> response 413. But the CGI only reads 8000 bytes, and the rest is not read.

Did you take a network trace between httpd and the backend (pcap with wireshark 
or tcpdump)?
Are the remaining bytes actually sent by httpd or not?

>
> When we use the same server with secure web pages running on port 443, 
> the CGI reads all blocks other than the first 8000 bytes.

I don't see how (for now) it could depend on the client's side type of 
connection (TLS or not).
The dumpio traces show that in both cases the whole content is received by 
httpd, so let's see with network traces whether it's been sent on the other 
side.


Regards,
Yann.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


Reply via email to