It’s situationally better, but in most instances, a 302 redirect might be preferable since search engines can stumble over 307s.
We’re getting pretty far into the weeds, but here goes my long-winded response. The difference between a 302 and a 307 is that the 307 retains the query’s “method,” whereas the 302 does not pass along the method.
There’s the GET method and the POST method. An example of GET is a typical hypertext link that calls up a web page. In other words, the browser gets information from the browser to build the web page. An example of POST might be sending form data to the server. In other words, the browser posts information to the server.
GET can also be used to transfer actionable information to the server, but that information is appended to the URL. When the need to transfer information to the server exceeds the inherent limitations of GET, POST must be specified, and the information transferred within the request body.
GET is the default and isn’t typically specified unless there’s reason to believe that POST is needed, in which case POST is specifically specified.
A 302 temporary redirect doesn’t maintain the method, but off the top of my head, I can’t think of a typical situation where a redirect would need to transfer POST data. I’m sure that an oddball situation might exist, but I’ve never run into it, so I’ve never had occasion to use a 307 redirect.
The biggest problem with 307 redirects, however, is that unlike GET, search engine bots can stumble over POST requests due to situationally important information being absent from the appended information on URLs. But from what I understand, the bots have gotten much better at extracting that information from the body of POST requests. Then again, I can’t think of too many situations where one would want a POST request indexed.
In essence, using 302 or 307 makes little difference unless there’s a specific reason to retain the POST method, in which case 307 is needed. I’d rather use 302 because GET is still the default. By the way, this is an example of the type of deep-in-the-weeds technical stuff that has caused me to shift away from building websites, which used to be my primary design specialty for several years. I found it less and less fun to deal with.