Re:
by pixelesque on Sunday April 23, 2023 @05:00PM
(#35680575)
Bing crawler does in my limited experience seem pretty picky... It doesn't even seem to be able to follow HTTP->HTTPS 308 redirects on one of my sites (it has successfully indexed another) - it makes requests to http:// for my site, gets a 308 redirect to https://, and then does nothing with that, other than robots.txt requests.
[ Parent
| on HN ]
because thats not the right way to do that. just look at the site you are on right now:
> curl -i http://news.ycombinator.com/
HTTP/1.1 301 Moved Permanently
Location: https://news.ycombinator.com/
Re:
by pixelesque on Sunday April 23, 2023 @07:09PM
(#35681659)
As far as I'm aware (I have read up on it), 308 is a newer and just as acceptable way of doing it, and in fact it's what Caddy (the webserver I'm using) uses for its built-in HTTP->HTTPS redirect functionality...
https://www.rfc-editor.org/rfc/rfc7538
It does seem possible/likely that Bing doesn't understand this though and only understands 301...
Re:
by handsclean on Sunday April 23, 2023 @07:58PM
(#35682007)
308 is the right way to do it, 301 is the old and slightly buggy way. Specifically, 301 lets a POST get redirected as either a GET or a POST, “for historical reasons”, while 308 guarantees no changes. 308 is not exactly edgy, either, it’s been supported by every browser since 2015.