diff --git a/content/posts/2019-11.md b/content/posts/2019-11.md
index 0af69d2c0..6640a9c8a 100644
--- a/content/posts/2019-11.md
+++ b/content/posts/2019-11.md
@@ -288,5 +288,19 @@ $ http "http://localhost:8081/solr/statistics/select?q=userAgent:/Scrapoo\/[0-9]
 ```
 
 - Nice, so searching with regex in Solr with `//` syntax works for those digits!
+- I realized that it's easier to search Solr from curl via POST using this syntax:
+
+```
+$ curl -s "http://localhost:8081/solr/statistics/select" -d "q=userAgent:*Scrapoo*&rows=0")
+```
+
+- If the parameters include something like "[0-9]" then curl interprets it as a range and will make ten requests
+  - You can disable this using the `-g` option, but there are other benefits to searching with POST, for example it seems that I have less issues with escaping special parameters when using Solr's regex search:
+
+```
+$ curl -s 'http://localhost:8081/solr/statistics/select' -d 'q=userAgent:/Postgenomic(\s|\+)v2/&rows=2'
+```
+
+- I updated the `check-spider-hits.sh` script to use the POST syntax, and I'm evaluating the feasability of including the regex search patterns from the spider agent file, as I had been filtering them out due to differences in PCRE and Solr regex syntax and issues with shell handling
 
 <!-- vim: set sw=2 ts=2: -->
diff --git a/docs/2019-11/index.html b/docs/2019-11/index.html
index be9c801b9..ec6dfded6 100644
--- a/docs/2019-11/index.html
+++ b/docs/2019-11/index.html
@@ -34,7 +34,7 @@ Let&rsquo;s see how many of the REST API requests were for bitstreams (because t
 <meta property="og:type" content="article" />
 <meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-11/" />
 <meta property="article:published_time" content="2019-11-04T12:20:30+02:00" />
-<meta property="article:modified_time" content="2019-11-12T11:44:05+02:00" />
+<meta property="article:modified_time" content="2019-11-13T18:18:24+02:00" />
 
 <meta name="twitter:card" content="summary"/>
 <meta name="twitter:title" content="November, 2019"/>
@@ -73,9 +73,9 @@ Let&rsquo;s see how many of the REST API requests were for bitstreams (because t
   "@type": "BlogPosting",
   "headline": "November, 2019",
   "url": "https:\/\/alanorth.github.io\/cgspace-notes\/2019-11\/",
-  "wordCount": "1819",
+  "wordCount": "1951",
   "datePublished": "2019-11-04T12:20:30+02:00",
-  "dateModified": "2019-11-12T11:44:05+02:00",
+  "dateModified": "2019-11-13T18:18:24+02:00",
   "author": {
     "@type": "Person",
     "name": "Alan Orth"
@@ -446,11 +446,27 @@ $ http &ldquo;<a href="http://localhost:8081/solr/statistics/update?commit=true&
 $ http &ldquo;<a href="http://localhost:8081/solr/statistics/select?q=userAgent:Scrapoo*&quot;">http://localhost:8081/solr/statistics/select?q=userAgent:Scrapoo*&quot;</a> | xmllint &ndash;format - | grep numFound
   <result name="response" numFound="1" start="0">
 $ http &ldquo;<a href="http://localhost:8081/solr/statistics/select?q=userAgent:/Scrapoo/[0-9]/&quot;">http://localhost:8081/solr/statistics/select?q=userAgent:/Scrapoo/[0-9]/&quot;</a> | xmllint &ndash;format - | grep numFound
-  <result name="response" numFound="1" start="0">
+  <result name="response" numFound="1" start="0"></p>
+
+<pre><code>
+- Nice, so searching with regex in Solr with `//` syntax works for those digits!
+- I realized that it's easier to search Solr from curl via POST using this syntax:
+
+</code></pre>
+
+<p>$ curl -s &ldquo;<a href="http://localhost:8081/solr/statistics/select&quot;">http://localhost:8081/solr/statistics/select&quot;</a> -d &ldquo;q=userAgent:<em>Scrapoo</em>&amp;rows=0&rdquo;)</p>
+
+<pre><code>
+- If the parameters include something like &quot;[0-9]&quot; then curl interprets it as a range and will make ten requests
+  - You can disable this using the `-g` option, but there are other benefits to searching with POST, for example it seems that I have less issues with escaping special parameters when using Solr's regex search:
+
+</code></pre>
+
+<p>$ curl -s &lsquo;<a href="http://localhost:8081/solr/statistics/select'">http://localhost:8081/solr/statistics/select'</a> -d &lsquo;q=userAgent:/Postgenomic(\s|+)v2/&amp;rows=2&rsquo;
 ```</p>
 
 <ul>
-<li>Nice, so searching with regex in Solr with <code>//</code> syntax works for those digits!</li>
+<li>I updated the <code>check-spider-hits.sh</code> script to use the POST syntax, and I&rsquo;m evaluating the feasability of including the regex search patterns from the spider agent file, as I had been filtering them out due to differences in PCRE and Solr regex syntax and issues with shell handling</li>
 </ul>
 
 <!-- vim: set sw=2 ts=2: -->
diff --git a/docs/sitemap.xml b/docs/sitemap.xml
index a63ac8458..f39beb64c 100644
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@@ -4,27 +4,27 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/categories/</loc>
-    <lastmod>2019-11-12T11:44:05+02:00</lastmod>
+    <lastmod>2019-11-13T18:18:24+02:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/</loc>
-    <lastmod>2019-11-12T11:44:05+02:00</lastmod>
+    <lastmod>2019-11-13T18:18:24+02:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/categories/notes/</loc>
-    <lastmod>2019-11-12T11:44:05+02:00</lastmod>
+    <lastmod>2019-11-13T18:18:24+02:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/2019-11/</loc>
-    <lastmod>2019-11-12T11:44:05+02:00</lastmod>
+    <lastmod>2019-11-13T18:18:24+02:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
-    <lastmod>2019-11-12T11:44:05+02:00</lastmod>
+    <lastmod>2019-11-13T18:18:24+02:00</lastmod>
   </url>
   
   <url>