Cyber security, infotech
[Updated 2019-03-17] Are you wondering why some JavaScript code from external domains simply won’t execute on your website? The reason could be as simple as an overly restrictive Content Security Policy (CSP for short). This article explains how you can create a Content Security Policy that’s both protective and functional. It will help you to secure your web server from some types of cross-site request forgery (XSRF/CSRF/XFS), clickjacking and other code injection attacks.
The Amazon Link plug-in for WordPress implements geotargeting based on ip2nation, a free geotargeting library from Per Gustafsson Consulting (available here). If you are wondering what you need to do in order to integrate the Amazon Link affiliate plug-in for WordPress (seing how a separate installation plugin for WordPress is two years old as of this writing, and counting), here is a quick howto for those who can access their websites’ MySQL or MariaDB database servers.
There are two major no-nos when it comes to writing NGINX redirects:
Instead, use ol’ good location blocks. But what if you have plenty of URIs to redirect? How do you deploy RegEx magic with NGINX? Easy.
Are you concerned about the security of data transmissions in which your web server participates day in and day out? Passwords, user names, credit card numbers, and other sensitive private communications on the Internet can easily be compromised unless you actively take precautionary measures and preempt the most common exploits by means of modern cryptography. Your users trust that you will protect them. The only question is: how do you measure success?
Have you ever seen one of these weird redirects? WordPress, for example, may refuse to show the log-in page, leaving you out of its admin interface for good. Here is what to do about it.