Using seeOther on a PUT Request redirects into a PUT request

I am using the POST/Redirect/GET pattern in my web application. It works as intended in a POST request. However when I return a Response.seeOther(uri) in my PUT request, it redirects into the same PUT request instead of the GET with the same URL(and I get a too many server redirects exception). I am not sure about the HTTP specification but isn't this a viable use case? Shouldn't POST/Redirect/GET be applicable to PUT/Redirect/GET?

Start by reproducing the reported PUT request that returns Response.seeOther(uri), then trace Jersey's redirect handling for the resulting response. Compare the observed method preservation with the expected POST/Redirect/GET behavior and identify the relevant HTTP specification requirements; done means the redirect behavior is explicitly resolved and covered by a regression test.

Written by the indexing model from the issue text.