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
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”); } }
Use the location header flag: curl -L <URL>
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.
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
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
If all you want to do is follow redirects but still want to use the built-in HTTP and HTTPS modules, I suggest you use https://github.com/follow-redirects/follow-redirects. yarn add follow-redirects npm install follow-redirects All you need to do is replace: var http = require(‘http’); with var http = require(‘follow-redirects’).http; … and all your requests will automatically follow … Read more
Update 2014-Jun-27: RFC 7231, Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, has been published as a PROPOSED STANDARD. From the Changelog: The syntax of the Location header field has been changed to allow all URI references, including relative references and fragments, along with some clarifications as to when use of fragments would not be appropriate. … 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