Ticket #10964 (closed PLIP: wontfix)
Asynchronously fetch suggestions for 404 Not Found page
Reported by: | ldr | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | JavaScript | Version: | |
Keywords: | Cc: | plip-advisories@… |
Description (last modified by ldr) (diff)
Proposer: Laurence Rowe (svn:ldr, irc:elro)
Seconder: None as yet
Motivation
Search engines indexing your site and bots trawling for ASP/PHP security holes can add a significant load to your site. Plone's 404 Not Found page is slow to render as it performs a catalogue search, which exacerbates the problem.
Proposal & Implementation
Change the not found template to fetch the suggestions asynchronously with javascript so only humans see the results.
Deliverables
Template change, Javascript.
Risks
What are the risks of implementing this proposal?
Might this affect SEO? ...provides links to pages that may have moved to crawlers.
What incompatibilities can it cause?
Existing customizations should continue to work just fine.
Participants
Laurence Rowe
Progress
None as yet.
Change History
comment:2 Changed 6 years ago by ldr
- Description modified (diff)
Async implies javascript. I would have said AJAX, but I don't intend to use any XML.
comment:3 Changed 6 years ago by hannosch
This PLIP doesn't make a lot of sense. The 404 page in Plone 4 does not contain a catalog search anymore as noted by hoss.
comment:4 Changed 6 years ago by limi
Yes, I think this PLIP should be rephrased as adding e feature back in, in an async implementation.
FWIW, I was unhappy to see this disappear, and it would be great to get it back without the synchronous hit from scripts posting to 404 pages.
comment:7 Changed 5 years ago by rossp
- Status changed from new to closed
- Resolution set to wontfix
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
- are still appropriate/needed
- still have owners/proposers/champions
- still have available implementers
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.
Perhaps a silly question: but how does fetching asynchronously avoid the site burden of 404-related site-trawling? The request still triggers the fetch.
Here's a related bug: http://dev.plone.org/plone/ticket/8667
And the changelist that addressed it: http://dev.plone.org/plone/changeset/36376
The changelist appears to have removed the suggestions portion of the 404 page altogether (which makes sense in the context of that bug discussion).