It breaks behavior in some misbehaving HTTP/1.0 clients at the time the HTTP/1.1 RFC was written.
I'm not sure that that's a signficiant concern now.
Still, if the behavior has changed, 301 isn't appropriate for other reasons, and if it hasn't changed, you shouldn't need a redirect at all, just handle requests to the old URL.
I'm not sure that that's a signficiant concern now.
Still, if the behavior has changed, 301 isn't appropriate for other reasons, and if it hasn't changed, you shouldn't need a redirect at all, just handle requests to the old URL.