301 Redirects vs. 302 Redirects

Status 301 means that the resource (page) is moved permanently to a new location. The client/browser should not attempt to request the original location but use the new location from now on. (Mostly 301 vs 302 is important for indexing in search engines, as their crawlers take this into account and transfer PageRank when using 301)

Status 302 means that the resource is temporarily located somewhere else, and the client/browser should continue requesting the original url.

NOTE: becareful about your page rank when redirecting!

#redirect #301 #302

When you redirect in nginX you would use one of 302, 301 code like the below code:

location = /singup {
     return 302 https://docs.google.com/forms;
 }

But there is tiny tip here that needs to be told. If you want to pass parameter to the destination link, which in here is https:// docs.google.com/forms it wont work. String parameters are being held in $args varaible in nginX so you need to pass this variable like the following code:

location = /singup {
     return 302 https://docs.google.com/forms$is_args$args;
 }

The variable $is_args value will be set to "?" if a request line has arguments, or an empty string otherwise.


#nginx #web_server #redirect #302 #is_args #args