switch from 'redirect:' prefix to ResponseEntity for redirecting UI index

[d3ns0n]

fixes #1100

[d3ns0n]

I would like to add some tests for this, but I didn't manage to succeed. The existing tests, that check the Location header e.g. test.org.springdoc.ui.app1.SpringDocRedirectDefaultTest, already check for a relative path but I don't understand why these tests worked before. I suspect that it has something to do with how @SpringBootTest is spinning up the application server during the tests. Feedback and Suggestions are welcome as I would really like to make sure that the Location header is set properly.

[bnasslahsen]

@d3ns0n,

Thank for your contribution.
I would prefer also the switch from redirect: prefix.

The tricky issue you had reported may need better integration tests.

As far as the existing tests are passing, i will accept PR.

[d3ns0n]

I was wondering if HTTP 302 is the proper response code as springdoc-openapi-webflux-ui returns 307 for the same use case. I found this on MDN

The only difference between 307 and 302 is that 307 guarantees that the method and the body will not be changed when the redirected request is made. With 302, some old clients were incorrectly changing the method to GET: the behavior with non-GET methods and 302 is then unpredictable on the Web, whereas the behavior with 307 is predictable. For GET requests, their behavior is identical. -- https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/307

So it wouldn't really change anything in this case since we only allow GET requests, but maybe we should make the return code consistent. What do you think?

[bnasslahsen]

@d3ns0n,

I had the same thoughts. I think http 302 is much better.
About making the change consistent, i also identified this action, but if you can propose an additional PR for webflux as well, it will be great!

[d3ns0n]

I will propose a PR later tonight