What can I say, upkeep sucks. I had made a number of changes as I migrated this blog from one platform to another. After the migrations, I even made some changes to WordPress. After making all of those changes, everything was broken but it didn’t matter. I had lots of leftover static content that allowed the broken links to function or so I thought. After making my blog searchable, I had a friend of mine reach out, David, reached out to let me know that I had some broken links....
Finally, my blog is searchable! I have added enough content that scrolling endlessly through categories wasn’t enough anymore. What Directions I Used As you might recall from my Successfully Deploying a Static WordPress Site post, I moved over to using Simply Static Pro to make my WordPress static. I finally got around to actually looking at the Set up search instructions and everything is live! How Did I Enable Search The directions above tell you to enable fuse and put `` into your page....
If you’ve followed my previous posts, you’ll see that I’ve spent some time attempting to build my blog on WordPress and then finally make it static. This had resulted in lots of custom code and even more failed attempts to get things to publish correctly. I’ve finally been successful in building out my site with a combination of some of my failed attempts: Adding Nginx in Front of WordPress Building a Kubernetes Container That Synchs with Private Git Repo Building a Static WordPress The third article above is the most failed attempt to date at making the WordPress site static because it resulted in just as many successes as it did failures....
In my Getting Started With a Content Security Policy post, I setup a report only CSP policy so that I could try and identify things that could test out a policy before implementing it. It is time to parse through the results and see what needs to be updated in my deployed policy. The original policy was very simple default-src https Inspecting The Violations I started trying to look at the current violations and I think it was clear that I had a rather permissive Content Security Policy because nothing much was being blocked....
I recently needed to setup Content Security Policy (CSP) on a website and I couldn’t think of where to get started. The first question that came to mind was what all content do I allow and how do I test everything without having to look through all of the code on the site. This is where the Content-Security-Policy-Report-Only header can come into play. The short version is that this allows you to create a policy in report only mode and you can collect the results at the endpoint specified via the report-uri directive....