Customize 403 page

Hi,

I am not sure what does custom 403 page has anything to do with cache plugin …

if you need to customize that , it is more appropriate to contact your hosting provider

Best regards,

When traffic is restricted at Quic.cloud CDN level, a 403 page with Quic.cloud logo is shown for blocked incoming visitors. I was asking about either customizing that page to display a custom logo and content instead, or to be able to perform a redirect to a different page or domain.

Hi,

if the 403 occurs on QC due to settings on QC (like blacklist or recaptcha fail …etc) that page, currently , is not customizable

if the 403 error was caused by origin server , in that case, you can follow standard Apache way to customize it

Best regards,

It is obviously the one on the quic.cloud I am referring to since it contains the QC logo. So, hmm, it is not nice, since the 403 forbidden error refers to a domain of mine, which is also shown in the address bar on the browser. Can I hope for a change here? Customize or redirect this?

Hi,

I can forward it to our devs as feature requests

it’s typical/default behaviors for many CDN providers though.

Best regards,

I really don’t see the sense in putting a CDN logo on someone else’s domain. What is the point in doing that, or prevent redirecting and customization?

I really hope that this gets changed.

Please send this to the decision making team, if it is not too much to ask.

Thank you for your support.

Hi,

don’t see the sense in putting a CDN logo on someone else’s domain

well , consider it as industrial standard behavior , e.g.

or

or

….etc

because if redirects to origin server then it’s kind of defeat the purpose to use CDN to deny/block requests

think it like if you have an ongoing DDoS attack with hundreds if not thousands requests come in simultaneously and redirect back to your origin server, then it could just easily be overwhelmed , even it’s just static requests.

another option is to set custom error page at CDN level , but that’s something currently not available and requires quite some work to get it which is what I have mentioned above as feature requests for our devs.

Best regards,

I understand the security concern. You are right. And the complexity of customization. But this last one, I think, should be allowed as long as this message is served under the owner’s domain… I mean, at minimal, at least a custom message should be allowed, and no CDN logo. Unless this is a form of advertising… But then again, to whom to advertise? To those who are actually intending of breaching the security?! Just thoughts.

Anyway, thank you for your support! I hope this gets an echo somewhere.