The answer above will work, you need to generate a self signed cert (or have a real one) and configure nginx as such: server { listen *:443; ssl on; server_name domain.com; rewrite ^(.*) http://domain.com$1 permanent; ssl_certificate /data/certs/domain.crt; ssl_certificate_key /data/certs/domain.key; } Keep in mind, if it is a self signed cert the browser will give you … Read more
If you faced such problem there’s a slight chance that you might need to revise your designs. This is a restriction of HTTP that POST data cannot go with redirects. Can you describe what are you trying to accomplish and maybe then we can think about some neat solution. If you do not want use … Read more
You mean how do browsers handle it? The server sends a 302 code along with a Location header, and the browser requests the new URI specified by the Location header instead. Unlike 301 (Moved Permanently), the browser continues to use the original URI to do requests, in case the 302 code goes away
By definition (see RFC 2616), the HTTP 302 response code is the redirect code. Without it, the location header may be ignored. However, you can send an HTTP 401 response and still display output. Instead of redirecting the user to an error page, you could simply write your content you want to send in the … Read more
Open web.config in the directory where the old pages reside Then add code for the old location path and new destination as follows: <configuration> <location path=”services.htm”> <system.webServer> <httpRedirect enabled=”true” destination=”http://example.com/services” httpResponseStatus=”Permanent” /> </system.webServer> </location> <location path=”products.htm”> <system.webServer> <httpRedirect enabled=”true” destination=”http://example.com/products” httpResponseStatus=”Permanent” /> </system.webServer> </location> </configuration> You may add as many location paths as necessary.
I resolved this by opening dev tools (F12), click “Network”, then click the “Preserve log” checkbox, and make the request that results in the cached 301. Right-click the request that results in the 301 and click “clear browser cache”. Try again and then 301 should no-longer be cached.
Add an HttpServletResponse parameter to your Handler Method then call response.sendRedirect(“some-url”); Something like: @RestController public class FooController { @RequestMapping(“/foo”) void handleFoo(HttpServletResponse response) throws IOException { response.sendRedirect(“some-url”); } }
I had to solve this problem today myself, and came across this question. Some of the answers are useful (using TempData), but don’t really answer the question at hand. The best advice I found was on this blog post: http://www.jefclaes.be/2012/06/persisting-model-state-when-using-prg.html Basically, use TempData to save and restore the ModelState object. However, it’s a lot cleaner … Read more
Redirects are followed only if they use the same protocol. (See the followRedirect() method in the source.) There is no way to disable this check. Even though we know it mirrors HTTP, from the HTTP protocol point of view, HTTPS is just some other, completely different, unknown protocol. It would be unsafe to follow the … Read more