Closed Bug 783855 Opened 13 years ago Closed 7 years ago

Migrated image/attachment all need a REDIRECT to be fetched

Categories

(Developer Documentation Graveyard :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: teoli, Unassigned)

References

Details

(Whiteboard: [content-debt])

All migrated images/attachments need a REDIRECT when used in a page. E.g. on https://developer.mozilla.org/en-US/docs/CSS/linear-gradient there are 2 image links: https://developer.mozilla.org/@api/deki/files/5961/=linear-gradient.png https://developer.mozilla.org/@api/deki/files/3849/=lingradexample.png both lead to a REDIRECT to the new URLs: https://developer.mozilla.org/files/3537/linear-gradient.png https://developer.mozilla.org/files/2843/lingradexample.png This may lead up to 1.5s gain for pages with 1 to 8 attachment, more with pages with more attachments. This is a upper limit as these REDIRECT are fetched in parallel with other requests. We can edit these manually, but with have 1000s of these and the relation between old and new URLs is somewhere in the system as we perform a redirect.
Priority: -- → P2
Version: Kuma → unspecified
Component: Docs Platform → Editing
I was wondering about speed of image loading in canvas docs and other areas as well recently, but those images often have the final url already, it seems. Luke, can you or someone get us a list of pages that still use these old image links? (would do myself, I have no dump anymore) Basically, docs (the rendered content/last revision) which have "@api/deki/files" in the content, so that we can see how many pages are affected and if this is a content-debt that is worth to fix.
Component: Editing → Performance
Flags: needinfo?(lcrouch)
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [content-debt]
Looks like we can get the list via the admin interface: https://developer.mozilla.org/admin/wiki/document/?q=%40api%2Fdeki%2Ffiles
Flags: needinfo?(lcrouch)
Component: Performance → File attachments
Component: File attachments → General
Product: Mozilla Developer Network → Developer Documentation
Priority: P2 → P3
Closing; probably not actionable at this point.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.