ASL WAF update broke plesk pages

DarkF@der · Unread post by **DarkF@der** » Thu Jan 09, 2014 7:14 am

Hello,

I have enabled waf on de plesk port.
After the upgrade a couple plesk pages get a 404 on all machines

like the client backup page, the client ftp account page and also the client cert page.
These pages get a 404 page not found.
If i disable to use WAF on plesk ports it's all working again.

Greetz

Unread post by **scott** » Thu Jan 09, 2014 9:21 am

Is it because the URL's have @ in them?

DarkF@der · Unread post by **DarkF@der** » Thu Jan 09, 2014 9:27 am

yep they have. How to fix it i needed to disable waf to fix it.

DarkF@der · Unread post by **DarkF@der** » Fri Jan 10, 2014 1:49 pm

Any solution to this i really like to enable WAF on plesk panel

Unread post by **scott** » Fri Jan 10, 2014 4:01 pm

That @ is a reserved character in http, its the delimiter between a username/password and hostname in an HTTP Auth connection. Plesk is using that character in a way it shouldnt, and its out of compliance with the protocol. To "fix" that would mean breaking the Http auth.

Unread post by **mikeshinn** » Fri Apr 25, 2014 8:31 am

It looks like newer versions of Plesk are using this character correctly now.

faris · Unread post by **faris** » Sun Apr 27, 2014 6:53 am

as in 12+ ?

Atomicorp

ASL WAF update broke plesk pages

ASL WAF update broke plesk pages

Re: ASL WAF update broke plesk pages

Re: ASL WAF update broke plesk pages

Re: ASL WAF update broke plesk pages

Re: ASL WAF update broke plesk pages

Re: ASL WAF update broke plesk pages

Re: ASL WAF update broke plesk pages