Hacker News new | ask | show | jobs
by stanleydrew 5461 days ago
Ah, fair enough. They are indeed two different resources. Would you have a problem if I returned the actual representation rather than a 302?
1 comments

I don't have a 'problem' with it, this is just conceptual talk. But I'd still do it for SEO reasons.

If Google fetched /blog/current as containing the "Why I love REST" post and showed it to me, and the when I clicked the link I got "Why I think turtles are awesome", I'd be annoyed. A 302 fixes that in a more clean way than entries in robots.txt or similar tricks.

EDIT: Apparently Google messes that up and often associates the content with the source URL and not the destination URL. Disregard the previous paragraph.

Seems like people are mixing up ways of providing web services with overall site design and url friendliness......