4 ms·
A priory it seemed really ideal to use Go and React so that's good to know. That issue is something I'd hardly find out to happen if just looking up online, tha
by tempw 10y ago
A priory it seemed really ideal to use Go and React so that's good to know. That issue is something I'd hardly find out to happen if just looking up online, thanks for sharing.
- oelmekki 10y agoNote that it's not really about using go, but more about implementing routing on client side : you lose http status for non api urls, whatever the backend language is. But then again, when you have static pages for public facing (and indexed) pages, and you have proper http status for api requests, having or not http status on web client urls is not that a big deal, so that's probably why it's not often mentioned. The only problem it could cause is if someone makes a deep link to somewhere in your app, it will return a 200 status and will be indexed by bots, probably indexing login form for just any url, so that's the annoying point (huge trolling possibilities, btw, there :) ).
- tempw 10y agoIndeed there is this caveat and its exploitation possibilities. I appreciate the thorough insight, thanks for taking the time!