Topic: In ARM system, Apache2.4.6 http can't work when https is on

[iammmp]

Apache2.4.6
apr-1.4.8
openssl-1.0.1c
arm-linux-gcc4.4.4

Recently I cross compiled Apache2.4.6 to run in my ARM cpu, and I found that http can work well if only it's own port such as 80 is listened, but if add one more port to be listened in conf file, http fails. That means http is good, but after https is on, http stop working and https is good.
At the same time, I built the same apache2.4.6 in X86 gcc4.6.1, http and https can both work well.
In addition, I also tried apache1.3.33 in the same ARM system, http and https can work well too.
It seems like that in apache2.4.6, http can't work well if there is one more port listened in ARM system. Actually http port is listening and is established when using netstat to monitor it.

root@freescale /usr/local/apache/bin$ netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 :::www :::* LISTEN
tcp 0 0 :::443 :::* LISTEN
tcp 0 0 (null):www (null):3705 ESTABLISHED
tcp 0 0 (null):443 (null):3720 ESTABLISHED

Hope someone here can give some help if you also met the similar problem. Thanks.

[James Blond]

You need two Listen