自定義 404 頁的危險

One customer running a single WordPress was using a 4x vCPUs instance on Amazon AWS®. 但是 CPU 和負載使用率太高了, 沒有明顯的原因 (參觀人數合理). 然而: 每 404 引發了巨大的 CPU 和頻寬消耗! 進行了測試，並且 404 was replaced by a flat and tiny 324 bytes HTML file. The result: the instance size could be divided by two, so halving all expenses (including the bandwidth).

When using a custom 404-page: one should not forget that even a simple dead link to an image will trigger an expensive and huge HTML code being returned to the browser, resulting in sluggish speeds for the visitors as well!

換句話說: do not do it, even if it looks pretty to the eyes.