System Design > Backends For Frontend subtopic resource properly renamed but valid content exists at URI with typo

[alicecommits]

What is the URL where the issue is happening

https://roadmap.sh/system-design/backends-for-frontend@n4It-lr7FFtSY83DcGydX

What browsers are you seeing the problem on?

Chrome

Describe the Bug

• In PR fixed typo in .md filename for backends-for-frontend subtopic in Syst… #8129 , I fixed the typo that existed in the Backends For Frontend .md file (backens-for-frontend@n4It-lr7FFtSY83DcGydX --> backends-for-frontend@n4It-lr7FFtSY83DcGydX)
• I also double-checked the rest of the repo to see if backends (corrected spelling) was indeed used anywhere relevant, notably in the system-design.json file and the migration-mapping.json files. The spelling seen there is backends.
• However, I can see the resource is still not found.
  • The resource that is being fetched is still located at https://roadmap.sh/system-design/backends-for-frontend@n4It-lr7FFtSY83DcGydX
  • The resource we want is located at the URL with typo: https://roadmap.sh/system-design/backens-for-frontend@n4It-lr7FFtSY83DcGydX

I further investigated the different request/response headers, especially the ones relating to AWS CloudFront:

Request URL:
https://roadmap.sh/system-design/backends-for-frontend@n4It-lr7FFtSY83DcGydX
Request Method: GET
Status Code: 404 Not Found
Remote Address: 3.165.136.72:443
Referrer Policy: strict-origin-when-cross-origin
age: 59180
cache-control: max-age=0, must-revalidate
content-encoding: br
content-type: text/html; charset=UTF-8
date: Mon, 27 Jan 2025 23:32:56 GMT
etag: W/"c9a1-194aa177455"
last-modified: Mon, 27 Jan 2025 23:27:31 GMT
server: nginx/1.18.0 (Ubuntu)
vary: Accept-Encoding
via: 1.1 c40f54ba68fc84418ef3fa6fd68bc010.cloudfront.net (CloudFront)
x-amz-cf-id: oPL141bf7fzYCUPG4qPVxjNTgQJwkn8vz_NyY2djTI9pQ1RPZf417w==
x-amz-cf-pop: CDG52-P3
x-cache: Error from cloudfront
x-frame-options: SAMEORIGIN
:authority: roadmap.sh
:method: GET
:path: /system-design/backends-for-frontend@n4It-lr7FFtSY83DcGydX
:scheme: https
accept: text/html
accept-encoding: gzip, deflate, br, zstd
accept-language: fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7,pl;q=0.6
authorization: Bearer undefined
content-type: application/json
referer: https://roadmap.sh/system-design

I investigated further the Error from cloudfront in the context of 404 Resource Not Found, which indeed seems to be the fact that the URL is pointing to a resource that doesn't seem to exist in CloudFront.

I wanted to know if there was maybe some resource renaming on the CloudFront side of things that needed doing. I am new to large websites CDN, I don't exactly know how the URI/URL renaming mechanisms work in CloudFront - I found this Medium article that talks about URL rewriting using a lambda function (in the author's use case, they do so to systematically drop a specific portion of the URL): https://serprime.medium.com/aws-cloudfront-url-rewriting-422d4868b282.

For roadmap.sh, is there any content update pull/push mechanisms triggered between the content of the repo - in this case, the .md file resource itself - and the corresponding CloudFront content? Or is the renaming workflow following another mechanism?

Thanks in advance,

Output from browser console (if any)

No response

Participation

• I am willing to submit a pull request for this issue.