OK, now I’m getting a HIT with one URL and a BYPASS with a different URL. Neither URL is hyphenated. They are each open in different tabs in the same web browser.
The one that works:
Request URL: https://www.daniweb.com/programming/databases/threads/24929/dadabik/amp
Request Method: GET
Status Code: 200
Remote Address: 172.67.7.242:443
Referrer Policy: strict-origin-when-cross-origin
Response Headers:
age: 55211
alt-svc: h3-27=":443"; ma=86400
cache-control: max-age=31536000, public
cf-cache-status: HIT
cf-ray: 5a1cd5ff393795f9-SJC
cf-request-id: 0345e41384000095f95f2fc200000001
content-encoding: br
content-type: text/html; charset=UTF-8
date: Thu, 11 Jun 2020 16:51:17 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
status: 200
strict-transport-security: max-age=15552000; includeSubDomains; preload
vary: Accept-Encoding
x-content-type-options: nosniff
x-powered-by: PHP/7.2.19
Request Headers:
:authority: www.daniweb.com
:method: GET
:path: /programming/databases/threads/24929/dadabik/amp
:scheme: https
accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9
cache-control: max-age=0
cookie: _ga=GA1.2.798903330.1573012496; __gads=ID=d943cc029eb46fb8:T=1573012498:S=ALNI_MY4nKFz8Gm5cjaRCWgDHgYk4G9yxA; _gid=GA1.2.567037913.1586803065; __cfduid=df67c1543667406d9d43b1b2bcb7108371591128368; dani_ad=Square; dani_csrf=6aee13b3da3de1ffea08bf1c5c223fd2; connect=074037a19e1ce711651419d3b41bd72ad11946e2
referer: https://community.cloudflare.com/
sec-fetch-dest: document
sec-fetch-mode: navigate
sec-fetch-site: same-origin
sec-fetch-user: ?1
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
The one that doesn’t work:
Request URL: https://www.daniweb.com/programming/databases/threads/900/rebus/amp
Request Method: GET
Status Code: 200
Remote Address: 172.67.7.242:443
Referrer Policy: no-referrer-when-downgrade
Response Headers:
alt-svc: h3-27=":443"; ma=86400
cache-control: max-age=31536000, public
cf-cache-status: BYPASS
cf-ray: 5a1cdbecbe6195f9-SJC
cf-request-id: 0345e7c7f2000095f95f1a9200000001
content-encoding: br
content-type: text/html; charset=UTF-8
date: Thu, 11 Jun 2020 16:55:19 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Thu, 19 Nov 1981 08:52:00 GMT
pragma: no-cache
server: cloudflare
set-cookie: dani_csrf=6aee13b3da3de1ffea08bf1c5c223fd2; expires=Thu, 11-Jun-2020 18:55:19 GMT; Max-Age=7200; path=/; SameSite=Strict; domain=www.daniweb.com; secure; HttpOnly
status: 200
strict-transport-security: max-age=15552000; includeSubDomains; preload
vary: Accept-Encoding
x-content-type-options: nosniff
x-powered-by: PHP/7.2.19
Request Headers:
:authority: www.daniweb.com
:method: GET
:path: /programming/databases/threads/900/rebus/amp
:scheme: https
accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9
cookie: _ga=GA1.2.798903330.1573012496; __gads=ID=d943cc029eb46fb8:T=1573012498:S=ALNI_MY4nKFz8Gm5cjaRCWgDHgYk4G9yxA; _gid=GA1.2.567037913.1586803065; __cfduid=df67c1543667406d9d43b1b2bcb7108371591128368; dani_ad=Square; dani_csrf=6aee13b3da3de1ffea08bf1c5c223fd2; connect=074037a19e1ce711651419d3b41bd72ad11946e2; _gat=1
sec-fetch-dest: document
sec-fetch-mode: navigate
sec-fetch-site: none
sec-fetch-user: ?1
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
Late last night, I noticed that for some reason my web browser is sometimes sending the request header cache-control: max-age=-0. I don’t know why it’s doing that, and why it’s only doing it with some requests?? I’m using Chrome. I also updated Chrome today to the latest version, meaning that this problem persists even across multiple versions of Chrome.
However, I’m unsure if it’s related because you’ll notice that today, it sent that header with the URL that worked, and didn’t send that header with the URL that id not work. However, yesterday, if you look at the headers I copied/pasted yesterday, the opposite was true. That header was not included when it worked, and included when it didn’t work.
