Whenever we get a HTTP 302 error, it requires a redirect and the same questions usually arise:
Nayi eminye imibuzo:
- Ingabe iwebhusayithi yami isilungele?
- Uhlobo luni lokuqondisa kabusha olufanele kakhulu icala lami?
- Ingabe ngizolahlekelwa ngumsebenzi wonke we-SEO engiwenze kuze kube manje?
- Ingabe iGoogle izongijezisa? Kwenzekani uma ngiqeda ukuqondisa kabusha?
- Zenziwa kanjani?
- Ngililungisa kanjani iphutha 302? (uma kwenzeka)
Kulesi sihloko, ngizophendula yonke le mibuzo ukuze ucace ngokwengeziwe ukuthi uqhubeke esimweni ngasinye.
Kuyini 302 ukuqondisa kabusha?
Code 302 indicates a temporary redirection.
One of the most notable features that differentiate it from a I-301 iqondisa kabusha ukuthi, esimweni sokuqondisa kabusha okungu-302, amandla we-SEO awadluliselwa kwi-URL entsha.
Lokhu kungenxa yokuthi le ndlela yokuqondisa kabusha yakhelwe ukuthi isetshenziswe lapho kunesidingo sokuqondisa kabusha okuqukethwe ekhasini elingesilo elicacisayo.
Ngakho-ke, uma ukubuyiselwa kabusha sekuqediwe, ikhasi lokuqala lizobe lingalahlekanga isikhundla salo injini yokusesha yakwaGoogle.
Noma kungejwayelekile kakhulu ukuthi sizithole sidinga ukuqondiswa kabusha abangama-302, le ndlela ingaba wusizo kakhulu kwezinye izimo. Lawa amacala ajwayelekile kakhulu:
- Lapho sibona ukuthi kunokuqukethwe okungafanele ekhasini. Ngenkathi sixazulula inkinga, singathumela umsebenzisi kwelinye ikhasi elingaba nentshisekelo.
- Esimweni lapho ukuhlaselwa kwewebhusayithi yethu kudinga ukubuyiselwa kwanoma yiliphi amakhasi, lokhu okuqondisa kabusha kungasisiza ukunciphisa izehlakalo.
Ukuqondisa kabusha i-302 yikhodi etshela izivakashi ze-URL ethile yokuthi leli khasi lihanjiswe okwesikhashana, liqondise ngqo endaweni entsha.
Ngamanye amagama, kuqondiswe kabusha i-302 icushiwe lapho amarobhothi e-Google noma ezinye izinjini zokucinga zicela ukulayisha ikhasi elithile. Ngaleso sikhashana, ngenxa yalokhu kuqondiswa kabusha, iseva ibuyisa impendulo ezenzakalelayo ekhombisa i-URL entsha.
Ngale ndlela amaphutha nokucasulwa kuvinjelwa ukusesha izinjini kanye nabasebenzisi, okuqinisekisa ukuzula okubushelelezi.
Kuyini ukuqondisa kabusha i-302?
Ukuqondisa kabusha i-302 isebenza, ngokwesibonelo, ukuba nezinguqulo eziningana zekhasi lasekhaya ngezilimi ezahlukahlukene.
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.
Ngale ndlela, ukuhlanganisa web traffic kutholakala, kepha ngasikhathi sinye, ithonya elisezingeni le-SEO lekhasi eliyinhloko alihlanjulwanga. Lokhu kuyaqhubeka kukhula, noma kungekho ukudluliselwa kwegunya, njengoba sachaza ngaphambili.
Isibonelo sokuqondisa kabusha se-HTTP 302
The most common HTTP 302 redirect example case is Google.
Akunandaba nokuthi izwe ungena kuliphi, uma uthayipha kulo https://www.google.com/, you will be redirected to the Google version in the language/country that corresponds to you.
Uma kwenzeka iJalimane, i-302 isithatha ngokuzenzakalelayo https://www.google.de/ ukuze sikwazi ukucinga okuqukethwe ngesiJalimane.
Amaphothali ezinkampani eziphumelelayo ezifana neCoca-Cola noma iFujitsu nazo zisebenzisa lolu hlelo ukuqondisa kabusha ithrafikhi lapho ibheka khona ukuthi ilungele kakhulu.
What causes HTTP 302 error?
Here are some of the most common reasons for the 302 redirect error:
- Isebenzisa ukuqondisa kabusha okungu-302 ngenkathi isizinda sihamba;
- Ukwakha ukuqondisa kabusha uma ususa idokhumenti;
- Kusetshenziswe ukuqondiswa kabusha kwe-302 ngesikhathi sokushintsha kwesayithi;
- Ukwakha kabusha ama-302 ngenkathi ukwakhiwa kwesayithi kuyashintsha.
Ukuqondiswa kabusha kwe-HTML 302 akunconyelwanga lapho indlela yesicelo soqobo izosetshenziswa esicelweni se-URL yendawo okuyiwa kuyo - ngokwesibonelo, ukuhambisa i-URL yomyalelo wefomu osebenzisa indlela ye-POST yesikhathi esithile.
Akufanele usebenzise ikhodi yesimo 302 uma ufuna ukudlulisela isisindo se-SEO ku-URL oya kuyo.
How to identify HTTP 302 error?
Iqinisekisa ukuthi i-301 ne-302 iqondisa kabusha izilungiselelo zilungile Kulula kakhulu.
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.
Kukhona enye inketho - ukufaka isicelo sokuhlola ikhodi yokuphendula iseva ezinsizakalweni ze-inthanethi, ngokwesibonelo, i-http: //example.com/e_redirect/.
Uma uhlela ukuqondisa kabusha ngendlela efanele, ngemuva kokufaka igama lesizinda, uzobona ikhodi yokuphendula engu-301 noma u-302. Kuya ngokuthi uluphi uhlobo lokuqondisa kabusha ohlele ukulithola ekuqaleni.
Ezinye izinsizakalo zengeza zibonisa ikhodi enikezwe iseva ngemuva kokuqondisa kabusha, futhi kunendlela eyodwa kuphela evumelekile - 200 Kulungile.
How to fix HTTP 302 error?
Indlela yoku-1: Bheka ukucushwa kweseva
Uhlelo lokusebenza lungahle lusebenze kuseva esebenzisa enye yalezi zinhlelo ezijwayelekile ze-web server, i-Nginx noma i-Apache. Lezi seva ezimbili ze-akhawunti zisebenza ngaphezu kwamaphesenti angama-84 wohlelo lwe-web server yomhlaba wonke!
Therefore, the first step in determining the 302 response code is checking the mandatory redirect instructions in the webserver program configuration file.
Ye-Apache web Server
Isinyathelo 1: Vula ifayela le-.htaccess kuseva
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.
Uma uhlelo lwakho likusingathi esabiwe, ungahle igama lakho lomsebenzisi lixhumeke kwi-akhawunti yomsingathi, ngokwesibonelo. Kulokhu, imvamisa, isikhombimsebenzisi sezimpande zohlelo lokusebenza sitholakala emzileni:
/home/<username>/public_html/path, thus the .htaccess file is located at /home/<username>/public_html/.htaccess.
Isinyathelo 2: Thola izinkombandlela ze-mod_rewrite
Lapho usuthole ifayela le-.htaccess, ulivule ngombhalo-wokuhlela bese uthola umugqa osebenzisa i-RewriteXXX ticonditiones of module ye-Apache mod_rewrite.
Kodwa-ke, umqondo oyisisekelo ukuthi i-RewriteCond eyala ukuveza imodeli yombhalo eqhathaniswa ne-URL ebhalisiwe. Lapho isivakashi sicela i-URL ehambisanayo esizeni, isiqondisi se-RewriteRule esilandelela imiyalo eyodwa noma eminingi ye-RewriteCond siyothumela isicelo ku-URL ehambisanayo.
Isibonelo, okulandelayo kuyinhlanganisela elula yeRewriteRule neRewriteCond enelisa zonke izidingo ze- example.com, kepha esikhundleni salokho ifaka ukuqondiswa okwesikhashana ku-URI efanayo kusizinda sesikhashana - example.com:
Phinda ubhale ku-RewriteCond% {HTTP_HOST} ^ isibonelo \ .com $ RewriteRule ^ (. *) $ HTTP://www.temporter-example.com/EZ1 [R = 302]
Qaphela isibhengezo esingezansi ezansi kweRewriteRule, esibonisa ngokusobala ukuthi ikhodi yokuphendula kufanele ibe ngu-302, ikhombisa kumenzeli wesiphequluli ukuthi ukuqondisa kabusha okwesikhashana.
Isinyathelo 3: Setha kabusha izinkomba kufayela le-.htaccess
# BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^ index \ .php $ - [L] RewriteCond% {REQUEST_FILENAME}! -F RewriteCond% {REQUEST_FILENAME}! -D RewriteRule. /index.php [L] # END I-WordPress
Ngakho-ke, uma uthola i-RewriteRule engajwayelekile noma iRewriteCond ifayela lakho .htaccess elibonakala lingahambelani nalo, zama ukuwasusa okwesikhashana (prefixed ne #) bese uqala kabusha i-webserver ukubheka ukuthi inkinga ixazululiwe.
Kweseva ye-Nginx yewebhu
Isinyathelo 1: Vula ifayela le-nginx.conf
Uma iseva yakho yewebhu isebenza kwi-Nginx, kufanele ufune ifayela elihlukile kakhulu lokucushwa. Leli fayela lichazwa ngokuthi nginx.conf ngokuzenzakalelayo futhi litholakala kwesinye sezinkomba ezijwayelekile ezifakwe kuhlu ngezansi:
/ usr / wendawo / nginx / conf, / njll / nginx noma, / usr / wendawo / njll / nginx.
Isinyathelo 2: Bhala kabusha izinkomba kufayela le-nginx.conf
Ngemuva kokutholwa, vula ifayela le-nginx.conf kusihleli sakho sombhalo bese uthola izinkombandlela zokubhala kabusha ezihlobene nenkomba yokuqondisa kabusha.
Isibonelo, lokhu kungukuqondisa kwe-block block (kumenyezelwe isethi yezitatimende) esetha iseva ebonakalayo ngokukhiqiza ukuqondisa okwesikhashana kusuka ku-abc.com kuya kwesikhashana-abc.com:
iseva {lalela 80; lalela 443 ssl; iseva_name www.abc.com; bhala kabusha / / $ http://www.temporary-abc.com liqondise kabusha; }
Imiyalelo yokubhala ka-Nginx ifana ne-Apache RewriteRule futhi
Phinda ubhaleCond ngoba zivame ukuba nezindlela eziyinkimbinkimbi zokucinga ezisuselwa kumatheksthi.
Isinyathelo 3: Hlola inqubomgomo yokufaka ifayela le-nginx.conf
Kunoma ikuphi, hlola ifayela le-nginx.conf ukuthola inqubomgomo yokubuyisa esikhundleni equkethe ifulegi eliqondisa kabusha (enye ikhodi yokuphendula ngokuqhubekayo yefulegi 301).
Sicela uqaphele noma yikuphi okuhlukile ngaphambi kokuqala kabusha iseva ukuze uhlole ukuthi inkinga ixazululiwe yini.
Indlela 2: Sesha isoftware engakaphelelwa yisikhathi
Umbhalo obekiwe we-RFC we-HTTP 1.0 uthi inhloso yekhodi yokuphendula engu- “302 Found” ihloselwe ukukhombisa ukuthi iklayenti kufanele lenze ukuqondiswa okwesikhashana.
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.
Ukuxazulula le nkinga, idokhumenti ebekiwe ye-RFC HTTP 1.1 ibuyisele amakhodi wokuphendula angama-303, okunye ukuqondiswa okwesikhashana okungama-307, okuyindlela eqondakalayo yokuphatha i-POST-to-GET noma izimpendulo zesikhashana.
Indlela 3: Ukuhlanza Amalogi
Cishe zonke izinhlelo zokusebenza zewebhu zigcina amarekhodi kuseva. I-logi yohlelo lokusebenza imele ukumelela umlando wohlelo lokusebenza, okufana nokuthi amakhasi, amaseva aceliwe futhi axhunywa kanjani, atholakala kwidathabhethi enikeziwe, nokunye.
Izingodo zeseva zixhunywe kudivayisi yamanje esebenzisa izinhlelo futhi imvamisa iqukethe imininingwane ngesimo nangempilo yazo zonke izinsizakalo ezixhunyiwe, kanye nemininingwane mayelana neseva.
Irekhodi le-Google [PLATFORM_NAME] ku-CMS noma isebenzise i- [PROGRAMMING_LANGUAGE] ukubhalisa nokurejista i- [OPERATING_SYSTEM] lapho kwethulwa uhlelo lokusebenza langokwezifiso lolwazi olwengeziwe ukuthola lawa marekhodi.
Indlela 4: Lungisa ikhodi yokufaka isicelo
Kulesi simo, zonke izindlela okuxoxwe ngazo ngenhla ziyehluleka, inkinga ingahle ibe ikhodi yomsebenzisi yohlelo lokusebenza ebangele inkinga.
Zama ukuthola imbangela yenkinga ngesandla ukuthola uhlelo futhi uluhlaziye kuseva kanye namafayela wamalogi wohlelo.
Kungumqondo omuhle ukukopisha uhlelo lokusebenza olugcwele kukhompuyutha yakho yendawo yokuthuthukisa bese ungena kuyo ukuze ubone kahle ukuthi kwenzekani kumaski angama-302 ubone ikhodi yohlelo ngalunye.
HTTP 302 Error: Conclusion
Ekugcineni, njengoba usibonile, akudingeki sesabe okuningi ngamaphutha wokuqondisa kabusha we-HTTP 302. Ngaphandle kokuqhubeka nokunye, bayindlela enhle yokugwema ukulahlekelwa ukugcwala kumakhasi ethu e-inthanethi ngezinguquko ezingenakugwenywa ezivela eminyakeni edlule.
I hope that, after reading this article, you will not get chills every time about how do I fix the 302 moved temporarily error.
Noma ngabe ufuna ukufaka isandla kulokhu okuthunyelwe noma uma unombuzo noma ufuna nje ukunikeza umbono wakho, unganqikazi ukuphawula ngezansi!