Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The 410 gone code would be a useful response code in PM, for example for highly time-sensitive content that needs to "go away" when it's no longer relevant.
Setting to 7.x as I'm not sure if the PM will actually need D8 porting.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | http-410-response-drupal6-1722068-6.patch | 1.26 KB | jedihe |
| #3 | 1722068_3_add_410_gone_response_code.patch | 1.59 KB | Letharion |
| #1 | 1722068_1_add_410_gone_response_code.patch | 1.65 KB | Letharion |
Comments
Comment #1
Letharion commentedFirst attempt at patch.
Comment #2
merlinofchaos commentedI don't think 410 should be at the top of the list. It's not used often, I'd put it at the end of the list.
Comment #3
Letharion commentedY U NO FIND MY USE-CAZE TEH BEST?
;)
I moved the implementation down to the last of the 4xx's, but wanted to keep them together, I hope you agree with that. Will of course move it all the way down if that's preferred.
In the declaration, I kept the order, as otherwise I would break the nice descending sort.
Comment #4
merlinofchaos commentedWell, I meant on the visible list. I rearranged that and pushed.
Comment #5.0
(not verified) commentedIt's response code, not selection rule.
Comment #6
jedihe commentedJust backported the patch from #3 to D6 Ctools. Did it on top of 6.x-1.10.