Chii chinonzi HTTP 302 Kukanganisa & Ungagadzirisa sei? [Maitiro 4 Akaedzwa Anotsanangurwa]

Munyaya ino, ini ndichapindura iyi mibvunzo yese kuitira kuti iwe uve nekujeka kwakawanda kuenderera mune yega yega mamiriro.

Chii chinonzi 302 chinodzoreredzwa?

Code 302 indicates a temporary redirection.
One of the most notable features that differentiate it from a 301 redirect ndeyekuti, mune makumi matatu emitatu redireirect, simba reSEO harina kuendeswa kune URL nyowani.

Izvi zvinodaro nekuti redirection iyi yakagadzirwa kuti ishandiswe kana paine chinodiwa chekutumira zviri mukati peji izvo zvisingave izvo zvinonzwisisika.
Nekudaro, kana redirection ikabviswa, iyo yekutanga peji ingangodaro isina kurasikirwa nzvimbo yayo muGoogle yekutsvaga injini.
Kunyangwe zvisiri zvakanyanya kuwanda kuti isu tazviwana isu tiri kuda kutungamirwa 302, iyi sarudzo inogona kubatsira chaizvo mune dzimwe nguva. Iyi ndiyo kesi inowanzoitika:

• Patinoziva kuti pane zvisina kukodzera zviri pane peji. Patinogadzirisa dambudziko, tinogona kudzosera mushandisi kune rimwe peji ringave rinofarira.
• Muchiitiko chekuti kurwiswa kwewebsite yedu kunoda kuti kudzoreredze chero kwemapeji, iyi redirect inogona kutibatsira kudzikisa zviitiko.

Iyo redirect 302 ndiyo kodhi inotaurira vashanyi yeiyo chaiyo URL iyo peji yakafambiswa kwenguva pfupi, ichivatungamira yakananga kunzvimbo itsva.
Mune mamwe mazwi, redirect 302 inoshanda kana Google marobhoti kana dzimwe injini dzekutsvaga dzichikumbira kurodha yakatarwa peji. Panguva iyoyo, nekuda kweiyi redirection, sevha inodzoka mhinduro ye otomatiki inoratidza URL itsva.
Nenzira iyi zvikanganiso uye zvinotsamwisa zvinodzivirirwa ese maviri kutsvaga injini nevashandisi, achivimbisa kufamba kwakadzikama

Chii chinonzi redirect 302 ye?

Iyo redirect 302 inoshanda, semuenzaniso, kuve neshanduro dzinoverengeka dzepeji mune mitauro yakasiyana.
The main one can be in English, but if the visitors come from other countries then this system automatically redirects them to a page in their language.

Nenzira iyi, kukurudzira kwe dandemutande motokari inowanikwa, asi panguva imwecheteyo, pesvedzero iri paSEO level reiyo peji guru haina kuderedzwa. Izvi zvinoramba zvichikura, kunyangwe pasina kuendeswa kwechiremera, sezvatakatsanangura kare.

HTTP 302 redirect muenzaniso

The most common HTTP 302 redirect example case is Google.
Pasinei nenyika iyo yaunopinda, kana iwe ukanyora mukati https://www.google.com/, you will be redirected to the Google version in the language/country that corresponds to you.

Muchiitiko cheGerman, 302 inotitora kuenda https://www.google.de/ kuitira kuti tigone kutsvaga zvemukati muGerman.
Nzvimbo dzemakambani akabudirira akaita seCoca-Cola kana kunyange Fujitsu inoshandisawo sisitimu iyi kudzosera vatengesi kwavanofunga kuti ndeyakanyanya.

What causes HTTP 302 error?

Here are some of the most common reasons for the 302 redirect error:

• Kushandisa 302 redireketa iyo iyo dhata ichifamba;
• Kugadzira iyo 302 inodzosera kana iwe uchifambisa gwaro;
• Kushandisa iyo 302 redirect panguva yepositi protocol change;
• Kugadzira 302 redirections iyo site saiti iri kuchinja.

HTML redirect 302 haina kukurudzirwa kana nzira yekutanga chikumbiro ichaiswa pachikumbiro cheiyo URL yekusvikira - semuenzaniso, kufambisa iyo URL yefomu yekuraira iyo inoshandisa iyo POST nzira yenguva yakatarwa.
Iwe haufanirwe kushandisa iyo mamiriro kodhi 302 kana iwe uchida kuendesa SEO-uremu kune iyo URL yekuenda.

How to identify HTTP 302 error?

Kuzivisa kuti iyo 301 uye 302 inotungamira zvigadziriso ndizvo chaizvo iri nyore kwazvo.
When entering into the address bar of the old address, we observe what is happening.
The change of address indicates that everything is fine with the redirect.
The address remains the same – you need to look for the source of the problem, but first, we advise you to clean the cache and try again.

Pane imwe sarudzo - yekushandisa yekutarisa server server kodhi kumasevhisi epamhepo, semuenzaniso, http://example.com/e_redirect/.
Kana iwe ukamisa iyo redirect nenzira kwayo, mushure mekupinda muzita rezita, iwe uchaona mhinduro kodhi 301 kana 302. Zvinoenderana nerudzi rwe redirection yawakaronga kugamuchira pakutanga.
Mamwe masevhisi anowedzerawo kuratidza kodhi yakapihwa nevhavha mushure mekutungamira, uye pano pane saruro imwechete yakanaka - 200 OK.

How to fix HTTP 302 error?

Nzira 1: Tarisa uone server mamiriro

Iko kushandiswa kunogona kumhanya pane seva iyo inoshandisa imwe yeaya maviri akajairwa webhu zvirongwa, Nginx kana Apache. Aya maviri mawebhu server anogadzira anopfuura makumi masere neshanu muzana ezvepasi rose rewebhu server chirongwa!
Therefore, the first step in determining the 302 response code is checking the mandatory redirect instructions in the webserver program configuration file.

YeApache webhu Server

Nhanho 1: Vhura .htaccess faira pane seva

To identify the webserver, you need to find the key file. If you are using the Apache web server, locate the .htaccess file in your site’s root filesystem.

Kana chirongwa chako chiri pane yakagoverwa, unogona kunge uine zita rako rakabatanidzwa kune iyo account account, semuenzaniso. Mune ino kesi, kazhinji, dhairekiti yeye mudzi midzi inowanikwa munzira:
/home/<username>/public_html/path, thus the .htaccess file is located at /home/<username>/public_html/.htaccess.

Nhanho yechipiri: Tsvaga iyo mod_rewrite mirau

Paunenge uchinge wawana .htaccess file, vhura iro mune-zvinyorwa-uye wobva wawona iyo inoshandisa RewriteXXX mirayiridzo iri yeApache mod_rewrite module.

Nekudaro, iro zano repakati nderekuti iro RewriteCond rairaire rinotsanangura modhi yemhando iyo inoenzaniswa neiyo yakanyorwa URL. Kana mushanyi achikumbira iyo inoenderana URL pane saiti, iyo RewriteRule kuraira iyo inoteedzera imwe kana mbiri RewriteCond mirairo ichaendesa zvekare chikumbiro ichi kuenda kune inoenderana URL.
Semuenzaniso, zvinotevera mubatanidzwa uri nyore weRewriteRule uye RewriteCond uyo unogutsa zvese zvinodiwa semuenzaniso.com, asi panzvimbo pazvo unosenderedza chinjana chenguva imwechete muiyo URI mune yechinguvana dura - example.com:

RewriteEngine pane RewriteCond% {HTTP_HOST} ^ semuenzaniso \ .com $ RewriteRule ^ (. *) $ HTTP://www.temporter-example.com/EZ1 [R = 302]

Tarira mureza wakawedzerwa pazasi peRewriteRule, iyo inoratidza zvakajeka kuti kodhi yemhinduro inofanirwa kunge ichisvika makumi matatu nemakumi matatu, ichiratidza kune browser mumiriri kuti inongedzerwa kwenguva pfupi.

Nhanho 3: Dzosera iyo yekuraira mu .htaccess faira

# BEGIN WordPress RewriteEngine Pa RewriteBase / RewriteRule ^ index \ .php $ - [L] RewriteCond% {REQUEST_FILENAME}! -F RewriteCond% {REQUEST_FILENAME}! -D RewriteRule. /index.php [L] # END WordPress

Naizvozvo, kana iwe ukawana zvisingazivikanwe RewriteRule kana RewriteCond dhairekita rako .htaccess faira risingaratidze kunge rakakwanira, edza kuvaburitsa kwenguva pfupi (prefixed ne #) uye wotangazve webserver kutarisa kana nyaya yagadziriswa.

YeNginx dura rewebhu

Nhanho 1: Vhura iyo nginx.conf faira

Kana yako sevha sewebhu ichishanda paNginx, iwe unofanirwa kutsvaga faira rakasiyana zvachose rekugadziriswa. Iyi faira inotsanangurwa se nginx.conf nekukasira uye inowanikwa mune imwe yeanowanzozivikanwa zvinyorwa pasi apa:

/ usr / local / nginx / conf, / etc / nginx kana, / usr / local / etc / nginx.

Nhanho yechipiri: Nyora zvakare mirairo pane nginx.conf faira

Mushure mekuona, vhura iyo nginx.conf faira mune yako zvinyorwa zvinyorwa uye tsvaga inonyorwazve mirayiridzo inoenderana neye redirect chiratidzo.

Semuenzaniso, ichi chiratidzo chakavanzika chedanho (chakaziviswa seti yezvirevo) inomisa iyo sevha sevha kuburikidza nekugadzira iyo yekudzoreredza kubva kuabc.com kune yenguva-abc.com:

server {teerera 80; teerera 443 ssl; server_name www.abc.com; nyora zvekare / / $ http://www.temporary-abc.com redirect; }

Nginx inonyora zvekare mirairo inoenderana neApache RewriteRule uye
RewriteCond nekuti vanowanzo fananidza zvakati wandei magwaro ekutarisira ekutsvaga.

Nhanho 3: Tarisa iyo yekutsiva iyo danho re nginx.conf faira

Chero zvazvingaitika, tarisa iyo nginx.conf faira yekusarudzira yekudzora mutemo ine mureza weinotendera (imwe yekusaruta mureza kudzoka kupindura kodhi 301).

Ndapota cherekedza chero zvasara kunze kwekunge watanga server zvakare kuitira kuti uone kana dambudziko ragadziriswa.

Nzira yechipiri: Tsvaga yeyekunze-software software

Rugwaro rwekutsanangurwa kweRFC yeHTTP 1.0 inotaura kuti chinangwa che "302 Yakawanikwa" kodhi yemhinduro inoitirwa kuratidza kuti mutengi anofanira kudzoreredza kwenguva pfupi.

However, many new browsers will process the code 302 received through the POST request as an invalid GET request.
This has triggered snags and confusion with particular web server programs that attempt to force the browser to perform the right work when it needs to be redirected temporarily.
Kugadzirisa dambudziko iri, iro RFC HTTP 1.1 ratidziro gwaro rakadzosera makumi matatu emitatu mhinduro, imwe 303 yekugadzirisa patsva, iri nzira inonzwisisika yekugadzirisa POST-to-GET kana yenguva pfupi, mhinduro dzinononoka.

Nzira 3: Kuchenesa maLog

Anenge ese ese webhu akachengetedza zvinyorwa pane server. Rogi rekunyorera rinowanzomirira nhoroondo yekushandisa, senge iwo mapeji, maseva akakumbirwa uye akabatana, ayo akawanikwa kubva kune yakapihwa dhatabhesi, zvichingodaro.

Iwo sevha matanda akabatana kune ikozvino chishandiso chinomhanya zvirongwa uye kazhinji chine ruzivo nezve chimiro uye hutano hwese masevhisi akabatana, uyezve neruzivo nezve server.
Rekodhi reGoogle [PLATFORM_NAME] muCMS kana kushandisa [PROGRAMMING_LANGUAGE] kunyoresa uye kunyoresa [OPERATING_SYSTEM] pakuvhura tsika yekushandisa kuti uwane rumwe ruzivo kuti uwane marekodhi aya.

Nzira yechina: Gadzirisa kodhi yekushandisa

Muchiitiko ichi, nzira dzese-dzakakurukurwa pamusoro dzinotadza, dambudziko rinogona kunge riri mune yekushandisa kodhi yekushandisa iyo yakakonzera dambudziko.

Edza kuona chinokonzeresa dambudziko nekuzviwanira pachako kunyorera nekuchiongorora mudura uye faira rekupinda.
Iyo ipfungwa yakanaka kukopa iyo yakazara iyo inoshandiswa kune yako yemunharaunda yekombuta yekubudirira uye nhanho kuburikidza nayo kuti uone chaizvo izvo zvinoitika kune makumi matatu emakumi matatu scan uye uone kodhi yemashandisirwo ese.

HTTP 302 Error: Conclusion

Pakupedzisira, sezvawaona, isu hatifanirwe kutya kwakawanda pamusoro peiyo HTTP 302 kutungamira zvikanganiso. Pasina kuenda chero mberi, ivo inzira inonakidza yekudzivirira kurasikirwa traffic pamapeji edu ewebhu nekuchinja kusadzivirika kunovapo kwemakore.
I hope that, after reading this article, you will not get chills every time about how do I fix the 302 moved temporarily error.
Kunyangwe iwe uchida kuita mupiro kune iyo post kana kana iwe uine mubvunzo kana uchingoda kupa pfungwa yako, usazengurira kupindura pasi apa!