network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 9 months |
| seen | May 7 at 19:58 | |
| stats | profile views | 19 |
|
Jan 21 |
awarded | Popular Question |
|
Oct 2 |
accepted | Nginx https rewrite turns POST to GET |
|
Oct 2 |
comment |
Nginx https rewrite turns POST to GET @c2hoh My bad. I apologize for taking this so long. I understand where my stupidy lies. You are correct. When a user hits it with http it will always be a GET (getting resource e.g. display the webpage). The script I wrote was wrong with that http because the old configuration was special. Thanks! |
|
Oct 2 |
comment |
Nginx https rewrite turns POST to GET @c2h50h Thanks. Doing rewrite ^(.*) https://$http_host$1; and then on the next line return 307; has no effect. From what I understand as you pointed out in wiki, 307 will continue to serve POST. But it seems like the redirect will still result in 301/302 because of rewrite... |
|
Oct 2 |
comment |
Nginx https rewrite turns POST to GET @c2h50h Thanks. But any way to go around this problem? Any better way to route from proxy to internal (which is 80 by default)? I insist that this is not a common issue so my method is probably really bad so if there's a more practical setup please share :) |
|
Oct 2 |
comment |
Nginx https rewrite turns POST to GET Well for one this is not really a browser. Well you can say it's browser because it uses HTTP protocol..okay.. thats fine. But then again, it looks like this only happens if I were doing over this two-layer configuration. If I were to put the same configuration directly on the internal machine, and running the test there, it will not complain. But then again, how do people do it in their production? I would assume some people are doing similar thing, reverse 443 to some VM that may be running 80 only. If there is a better practice, I'd like to learn it and hear about it. |
|
Oct 2 |
comment |
Nginx https rewrite turns POST to GET @c2h50h I understand that the HTTP spec stated something similar like that. But what can I do in Nginx? I mean this is a trivial setup where people forward 443 to an internal 80 port, but they can still do PUT, POST, DELETE, GET. In my previous setup I didn't have this extra proxy at the front serving the crowd. I had the same configuration on the same internal server (our test server). That works fine. |
|
Oct 2 |
revised |
Nginx https rewrite turns POST to GET edited title |
|
Oct 2 |
asked | Nginx https rewrite turns POST to GET |
|
Aug 21 |
awarded | Teacher |
|
Aug 16 |
asked | Is it safe to configure SSL on nginx and keep apache untouch? |
|
Aug 15 |
answered | How do I tell Nginx to skip rewrite some specific location? |
|
Aug 15 |
asked | How do I tell Nginx to skip rewrite some specific location? |
|
Jul 18 |
accepted | Setting up puppetmaster: hostname was not match with the server certificate |
|
Jul 18 |
accepted | ntpd doesn't seem to sync at all |
|
Jun 15 |
awarded | Critic |
|
Jun 14 |
comment |
ntpd doesn't seem to sync at all @Zoredache I suspect no. This is a University server, so it is very likely they block them. Is there a way to change the port? Or is it wise to do so? I can manually do ntpdate, but might worth a while to dig down and setup the automated process... thanks for the help so far. |
|
Jun 14 |
comment |
ntpd doesn't seem to sync at all @Zoredache Thanks. I just included the log for that. Please take a look? Thanks! |
|
Jun 14 |
revised |
ntpd doesn't seem to sync at all added 728 characters in body |
|
Jun 14 |
asked | ntpd doesn't seem to sync at all |
