Solve Adult Content 302 Issue

Revision as of 18:51, 7 November 2007 by TedErnst (talk | contribs) (draft)



(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

<noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < </noinclude>('''[[PairDays?|?]]''') [[{{subst:PAGENAME}}]] ('''[[Who?|?]]''') {{JustTinyEditIcon|{{subst:PAGENAME}}}}<noinclude></big> __NOTOC__ == What (summary) == As described on [[ErrorLog#Google caching issue]], we are using a 302 temporary redirect for our Adult Content Splash page. This means that Google keeps the cached version of the page before we put the flag on it. This is bad and we need to fix it. == Why this is important == * On a normal page, if we have personal information and someone requests it off, we no-bot the page and google re-spiders at some point, removing that personal information. With our 302 response, google cannot re-spider and just keeps this personal information forever. * Our [[AdultContentPolicy]] says that we will no be showing these pages to google at all, and we're not following that policy. == [[DoneDone]] == == Steps to get to [[DoneDone]] == [[Category:DevelopmentTask]] </noinclude>