Alex Sung
Forum Replies Created
-
Dear Supports,
The problems have been identified and addressed through our email discussions.
A big shoutout to Usman for his proactive follow-up emails with me.
Cheers to the whole team.
Best Regards,
Alex SungHi Nathan,
I apologize for the late response. The issue with question 1 has been fixed by resetting the .htaccess file to the default WordPress settings.
However, the problem with question 2 still persists due to a conflict with another plugin (Translate WordPress with GTranslate) which causing it unable to load where Simply Schedule Appointments Booking Plugin short code has been implemented on the homepage (https://swha.online) only.
Would you be able to help to resolve the plugin conflict?

As for the Content Security Policy, it’s only implemented by default Cloudflare CDN, where the x-frame-options are set to SAMEORIGIN just as you recommended.
CSP scan result : https://showdns.net/csp-checker/swha.online
Best Regards,
Alex SungLately my site has been hit by waves of difference types of cyberattacks vectors. As a result, I’ve ramped up the security on the CDN, WordPress, and web hosting.
For the most part, I’ll stick to your recommendations. I really appreciate your time and effort.
Additionally, I have another feature request on the massive blacklist import (both manually and automatically) in which I’m not sure if you’d be interested in. If so, i may just start another thread.
Best Regards,
Alex SungThank you so much for your detailed clarification.
Scenario 1
In that case, it would be best to remove the predetermined CSP sections (highlighted in the image below) and instead label them as a custom header.
In this way, users can decide how they want to fill it out based on their specific needs.
It might also be helpful if you can help to create a guide on how users can manage their CSP.
Scenario 2
We shall also consider avoid generating lengthy fields mainly because users can do their own testing. If we make it too long, it could be hard to troubleshoot for cases that it may just crash the whole site.
Plus, it’s easier for them to preview and make quick adjustments without having to read through a complicated and lengthy field.
Even if user have a lot of custom header sections, you might want to think about rewriting your code to combine all those sections into one single header.
Best Regards,
Alex SungHi Support,
Thanks for your sharing.
In fact, based on the CSP level 2 & 3 there’s a lot of more customization I can add and tailor to fit according to the attacks vectors or secure the web application.
You can have a look at the reference links I shared below.
I believe you can add ten times more custom header sections without it causing too many issues.
Right now, I’m dealing with a limitation in the custom header sections for setting up the CSP policy.
I can’t wait for you to take my suggestion onboard and enhance that additional feature.
Reference Links
https://content-security-policy.com/
https://www.geeksforgeeks.org/javascript/content-security-policy-csp/
https://developer.chrome.com/docs/privacy-security/csp
https://www.w3.org/TR/CSP3/
Best Regards,
Alex Sung