Invalid command 'RPAF_SetHTTPS'

Question

Invalid command 'RPAF_SetHTTPS'

Closed this issue 5 years ago · 6 comments

apache2 on ubuntu 18.04 does not accept 'RPAF_SetHTTPS' or 'RPAF_SetPORT'

Answer 1 · 2019-09-25T15:26:31.000Z

the version in ubuntu - and debian for that matter - is based on 0.6 and not 0.8. the syntax between these versions is different. the old versions used RPAFSetHTTPS instead of RPAF_SetHTTPS

i've stumbled ove the same issue years before as well and was doubting my sanity ;)

either build it yourself or change the syntax to leave out the _ for all of the parameter

Answer 2 · 2019-09-25T17:27:54.000Z

I don't suggest using it in production either way. See #42

Answer 3 · 2019-09-25T18:38:32.000Z

We don't expose Apache direct access to any one. Only nginx can be direct accessed by client Il Mer 25 Set 2019, 19:27 Andrei D. <notifications@github.com> ha scritto:

…

I don't suggest using it in production either way. See #42 <#42> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#58?email_source=notifications&email_token=AF5GL35FVCG7F7XUXDA4AETQLONRZA5CNFSM4I2KZFRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7SWJRA#issuecomment-535127236>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF5GL37C5FQ77NVWZUTUCE3QLONRZANCNFSM4I2KZFRA> .

Answer 4 · 2019-09-26T04:28:54.000Z

It's not about exposing Apache to public view. It's about making sure that if you use KeepAlive in Apache, and you're proxying https (nginx) => http (apache), you will get mixed content issues / busted nginx cache eventually. You have to sacrifice keepalive in order to avoid the bug. Either way, I suggest using @AlexAT's patch for mod_remoteip from #42 instead. I also got CloudLinux to include it in their apache stack if you use it so no need for custom compile there.

Answer 5 · 2019-09-26T06:25:33.000Z

Thanks it's only related to set port and set https right ? Il Gio 26 Set 2019, 06:28 Andrei D. <notifications@github.com> ha scritto:

…

It's not about exposing Apache to public view. It's about making sure that if you use KeepAlive in Apache, and you're proxying https (nginx) => http (apache), you will get mixed content issues / busted nginx cache eventually. You have to sacrifice keepalive in order to avoid the bug. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#58?email_source=notifications&email_token=AF5GL34QFJJ7GYRSQBLNJUDQLQ3ARA5CNFSM4I2KZFRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7UHS2Y#issuecomment-535329131>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF5GL36YYQTOP55P4LGJD6DQLQ3ARANCNFSM4I2KZFRA> .

Answer 6 · 2019-09-26T09:02:36.000Z

Closing this issue, this is not the place to discuss support for old versions.