Waa maxay HTTP 302 Cillad & Sidee loo xallin karaa? [4 Qaababka Tijaabinta La Sharaxay]

Maqaalkan, waxaan uga jawaabi doonaa dhammaan su'aalahan si aad u hesho caddayn badan oo aad ku sii waddo xaalad kasta.

Waa maxay 302 wareejin?

Code 302 indicates a temporary redirection.
One of the most notable features that differentiate it from a 301 dib u habeyn ayaa ah in, haddii ay dhacdo 302 wareejin, xoogga SEO loo wareejiyo URL cusub.

Tan waxaa ugu wacan dib-u-kicintaan waxaa loogu talagalay in la isticmaalo marka loo baahdo in lagu wareejiyo waxa ku jira bogga aan noqon doonin midka qeexan.
Markaa, marka dib u wareejinta la tirtiro, bogga asalka ah lumin maayo booskiisa mashiinka raadinta Google.
In kasta oo aysan ahayn wax aan caadi ahayn in aan nafteena u baahanahay oo ah dib-u-wareejin 302 ah, doorashadan ayaa faa'iido u yeelan karta xaaladaha qaarkood. Kuwani waa kiisaska ugu badan:

• Markaan ogaanno inay jiraan waxyaabo aan habooneyn oo ku yaal bog. In kasta oo aan xallineyno dhibaatada, waxaan u weecin karnaa isticmaaleyga bog kale oo xiiso yeelan kara.
• Haddii ay dhacdo in weerar websaydhkeenu u baahan yahay dib u soo celinta bogag kasta, hagitaankan ayaa naga caawin kara yareynta dhacdada.

Beddelka 302 waa koodh u sheegaya booqdayaasha URL gaar ah in bogga loo wareejiyay si ku-meel-gaar ah, isagoo toos ugu toosinaya goobta cusub.
Si kale haddii loo dhigo, wareejin 302 ayaa shaqeyneysa markii robotyada Google ama matoorada raadinta kale ay codsadaan in lagu xiro bog gaar ah. Daqiiqadaas, Thanks to redirect, serverku wuxuu soo celiyaa jawaab otomaatig ah oo muujineysa URL cusub.
Sidan ayaa khaladaadka iyo xanaaqyada looga fogaadaa labadaba matoorada raadinta iyo isticmaaleyaasha, iyagoo damaanad qaadaya marin habsami leh.

Waa maxay wareegga 302?

Beddelka 302 wuxuu u adeegaa, tusaale ahaan, inuu haysto dhowr nooc oo bog-bog oo luqado kala duwan ah.
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.

Qaabkaas, abaabul of gaadiidka web waxaa la gaaraa, laakiin waqti isku mid ah, saameynta heerka SEO ee bogga ugu weyn lama milmay. Tani waxay sii wadaa inay sii korto, inkasta oo aysan jirin wareejin awood, sida aan horeyba u sharaxnay.

HTTP 302 tusaale wareejin

The most common HTTP 302 redirect example case is Google.
Ayadoon loo eegayn wadanka aad ka gasho, hadaad ku qorto https://www.google.com/, you will be redirected to the Google version in the language/country that corresponds to you.

Xaalada Jarmalka, 302 si otomaatig ah ayey noogu qaadanaysaa https://www.google.de/ si aan u raadin karno waxa ku qoran luqadda Jarmalka.
Bogagga shirkadaha guulaha sida Coca-Cola ama xitaa Fujitsu sidoo kale waxay adeegsadaan nidaamkan si ay ugu weeciyaan taraafikada halka ay u tixgeliyaan kuwa ugu habboon.

What causes HTTP 302 error?

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

• Adeegsiga 302 wareejin inta domainku socdo;
• Abuuritaanka 302 wareejin marka aad guurto dukumiintiga;
• Adeegsiga 302 wareejin inta lagu gudajiray bedelka borotokoolka goobta;
• Abuuritaanka 302 wareejin inta qaab dhismeedka uu isbedelayo.

HTML redirect 302 laguma talinayo marka habka dalabka asalka ah loo adeegsado dalabka URL ujeedka - tusaale, dhaqaajinta URL dardaaranka foomka kaas oo adeegsanaya habka POST muddo cayiman.
Waa inaadan adeegsan koodh lambar 302 haddii aad rabto inaad ku wareejiso miisaanka SEO-ga URL halka loo socdo.

How to identify HTTP 302 error?

Xaqiijinta in 301 iyo 302 dib loo wareejiyo dejintu waa sax waa mid aad u fudud.
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.

Waxaa jira ikhtiyaar kale - in la dalbado hubinta koodhka jawaabta server-ka ee adeegyada khadka tooska ah, tusaale ahaan, http://example.com/e_redirect/.
Haddii aad saxdo toos u wareejin, ka dib markaad gasho magaca domain, waxaad arki doontaa lambarka jawaab celinta 301 ama 302. Waxay kuxirantahay nooca redirect ee aad qorsheysay inaad hesho bilowga.
Adeegyada qaar ayaa waliba si dheeraad ah u muujinaya koodh uu siiyay server-ka kadib wareejintii, oo halkan waxaa jira hal ikhtiyaar oo ansax ah - 200 ok.

How to fix HTTP 302 error?

Habka 1: Hubi qaabeynta server-ka

Codsiga waxaa laga yaabaa inuu ku shaqeeyo server-ka adeegsanaya mid ka mid ah labadan barnaamijyada ugu caansan ee shabakadda, Nginx ama Apache. Labadan shabakadood websaydhada in kabadan 84 boqolkiiba barnaamijka adeega websaydhka adduunka!
Therefore, the first step in determining the 302 response code is checking the mandatory redirect instructions in the webserver program configuration file.

Loogu tala galay server-ka Apache

Tallaabada 1: Fur faylka .htaccess ee server-ka

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.

Haddii barnaamijkaagu ku jiro martigeliyaha la wadaago, waxaad lahaan kartaa magacaaga isticmaale ee ku xira koontada martigeliyaha, tusaale ahaan. Xaaladdan oo kale, sida caadiga ah, tusaha xididka dalabka wuxuu ku yaal jidka:
/home/<username>/public_html/path, thus the .htaccess file is located at /home/<username>/public_html/.htaccess.

Tallaabada 2: Raadi tilmaamaha mod_rewrite

Markaad hesho faylka .htaccess, ku fur qoraal-tafatiraha oo hel khadka khadka adeegsanaya dardaaranka RewriteXXX ee ka tirsan moduleka 'Apache mod_rewrite'.

Si kastaba ha noqotee, fikradda guud ayaa ah in Tilmaamaha RewriteCond ay soo bandhigayaan qaab qoraal ah oo loo barbardhigo URL diiwaangashan. Marka booqde uu codsado URL-ka la midka ah ee ku yaal barta, Dardaaranka RewriteRule kaas oo raadinaya mid ama dhowr tilmaamood ee RewriteCond ayaa dhab ahaantii u weecin doona dalabka URL u dhigma.
Tusaale ahaan, waxyaabaha soo socdaa waa iskudhaf fudud oo ah RewriteRule iyo RewriteCond oo qancinaysa dhammaan shuruudaha example.com, laakiin taa beddelkeeda ku meelaynta ku-meelgaar ah isla URL-ga ku meel gaarka ah - example.com:

Ku qoro RewriteCond% {HTTP_HOST} ^ tusaalayaal \ .com $ RewriteRule ^ (. *) $ HTTP://www.temporary-example.com/$1 [R = 302]

Ogeysiiska bannerka dheeriga ah ee hoose ee RewriteRule, oo si cad u muujineysa in lambarka jawaab celintu ay tahay inuu noqdo 302, adoo u muujinaya wakiilka biraawsarka inay tahay ku-wareejin ku meelgaar ah.

Tallaabada 3: Dib uheeg dardaaranka faylka .htaccess

# Bilow WordPress Ku qoritaanka qoraalka 'RewriteBase / RewriteRule ^ index \ .php $ - [L] RewriteCond% {REQUEST_FILENAME}! -F RewriteCond% {REQUEST_FILENAME}! -D RewriteRule. /index.php [L] # END WordPress

Sidaa darteed, haddii aad ka hesho dardaar aan caadi ahayn RewriteRule ama RewriteCond faylkaaga .htaccess ee aan u muuqanayn mid ku habboon, iskuday inaad si ku meel gaadh ah u sharaxdo (horay ugulaabtay #) oo dib u bilow webserver si aad u hubiso in arrinta la xaliyay.

Loogu talagalay shabakadda shabakadda 'Nginx'

Tallaabada 1: Fur faylka nginx.conf

Haddii server-kaagu uu ka shaqeynayo Nginx, waa inaad raadsataa faylka gabi ahaanba ka duwan qaabeynta. Faylkan waxaa loo cayimay inuu yahay nginx.conf si caadi ah waxaana laga helay mid ka mid ah tilmaamaha guud ee hoos ku taxan:

/ usr / maxalli / nginx / conf, / iwm / nginx ama, / usr / maxalli / iwm / nginx.

Tallaabada 2: Ku qor dardaaranka faylka nginx.conf

Baadhista ka dib, ku fur faylka nginx.conf qorahaaga qoraalka oo ka hel tilmaamaha dib-u-qori ee la xidhiidha tilmaame u-wareejinta.

Tusaale ahaan, kani waa hannaan cad oo xanniban (oo lagu dhawaaqay nidaam caddayn ah) oo dejinaya server-ka dalwaddii isagoo adeegsanaya ku-wareejin ku-meelgaar ah ka abc.com illaa ku meel-gaar ah-abc.com:

server {dhagayso 80; dhageyso 443 ssl; server_name www.abc.com; dib u qor ^ / $ http://www.temporary-abc.com redirect; }

Tilmaamaha regin-ka ee Nginx waxay barbar socdaan Apache RewriteRule iyo
RewriteCond maxaa yeelay had iyo jeer waxay ka kooban yihiin qaabab raadin raadinta ku saleysan qoraalka.

Tilaabada 3: Hubi siyaasadaha bedelka faylka nginx.conf

Si kasta ha noqotee, ka eeg faylka nginx.conf wixii laga reebayo siyaasadaha ka beddelashada ee ay ku jiraan calanka wareejinta (lambar kale oo jawaab celin caam ah oo 301 ah).

Fadlan la soco wixii ka reeban ka hor intaadan dib u bilaabin adeegaha si loo hubiyo in dhibaatada la xaliyay.

Habka 2: Ka raadi barnaamij-kombuyuutar oo waqtigiisu dhacay

Dukumentiga cayiman ee RFC ee HTTP 1.0 wuxuu sheegayaa in ujeedada “302 la helay” nambarka jawaab celinta loogu talagalay in lagu muujiyo in macmiilku uu fulinayo hagitaan kumeelgaar ah.

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.
Si loo xalliyo dhibaatadan, RFC HTTP 1.1 dukumiinti qaabeyn ayaa soo celiyay 303 lambar oo jawaab celin ah, 307 kale oo wareejin ku meel gaar ah, taas oo ah hab la fahmi karo oo loo maareeyo POST-to-GET ama jawaab ku meelgaar ah, jawaabaha ku meel gaarka ah.

Habka 3: Nadiifinta Logska

Ku dhawaad ​​dhammaan codsiyada websaydhku waxay ku keydiyaan diiwaannada server-ka. Diiwaanka arjiga ayaa sida caadiga ah matalaya taariikhda dalabka, sida boggaga, adeegaha la codsaday iyo ku xiran, ee laga helay keydka macluumaadka la bixiyay, iyo wixii la mid ah.

Diiwaanka meheradda ayaa ku xidhan aaladda hadda socota ee maamusha barnaamijyada oo sida caadiga ah ka kooban macluumaad ku saabsan xaaladda iyo caafimaadka dhammaan adeegyada ku xiran, iyo xitaa macluumaadka ku saabsan server-ka.
Ku duub Google [PLATFORM_NAME] gudaha CMS ama isticmaal [PROGRAMMING_LANGUAGE] si aad iskaga diiwaangeliso oo aad isaga diiwaangeliso [OPERATING_SYSTEM] markii ay bilaabayaan dalabka caadiga ah si loo helo macluumaad dheeraad ah si loo helo diiwaanadan.

Habka 4: Samee lambarka dalabka

Xaaladda jirta, dhammaan qaababka aan kor ku soo sheegnay way ku guul darreystaan, dhibaatadu waxay ku dhici kartaa koodhka isticmaalaha ee sababta keentay dhibaatada.

Isku day inaad go'aamiso sababta dhibaatada adoo gacanta ku haaya arjiga oo aad falanqayn ku sameysa serverka iyo faylasha diiwaanka.
Waa fikrad wanaagsan inaad nuqul ka mid ah u isticmaasho kombuyuutarkaaga horumarinta ee degmadaada oo aad uga gudubto si aad u aragto sida saxda ah ee ku dhici doona baaritaannada 302 oo aad u aragto koodh codsi kasta.

HTTP 302 Error: Conclusion

Ugu dambeyntii, sidaad aragteen, ma aha inaan wax badan ka cabsanno khaladaadka HTTP 302 Iyaga oo aan horay u sii socon, waxay yihiin hab cajiib ah oo looga fogaado inay ku lumiyaan taraafikada boggayaga leh isbeddelada lama huraanka ah ee ka soo baxa sannadaha.
I hope that, after reading this article, you will not get chills every time about how do I fix the 302 moved temporarily error.
Haddii aad rabto inaad tabaruc ku sameyso boostada ama haddii aad qabtid su'aal ama aad rabto inaad dhiibto fikirkaaga, ha ka labalabeyn inaad faallo ka bixiso hoosta!