Hōʻike: Ke kūʻai aku nei ʻoe i kahi lawelawe a huahana paha ma o kā mākou mau loulou, loaʻa iā mākou i kekahi manawa he komisina.

He aha nā hapa o HTTP 302 & pehea e hoʻoponopono ai? [4 nā ʻano hoʻāʻo ʻia i hōʻike ʻia]

Whenever we get a HTTP 302 error, it requires a redirect and the same questions usually arise:

Eia kekahi o nā nīnau:

  1. Ua mākaukau paha kaʻu pūnaewele nona?
  2. He aha ke ʻano o kahi hōʻano hou i kūpono i koʻu hihia?
  3. E nalowale anei au i nā hana SEO a pau aʻu i hana ai a hiki i kēia manawa?
  4. E hoʻopaʻi anei ʻo Google iaʻu? He aha ka mea inā e hoʻopau wau i ka hoʻihoʻi?
  5. Pehea lākou i hana ʻia?
  6. Pehea e hoʻoponopono ai i ka hala 302? (inā paha)


Ma kēiaʻatikala, e pane wau i kēia mau nīnau āpau a ʻoi aku ka nui o kou hoʻomaopopo ʻana e hoʻomau i kēlā me kēia hihia.

He aha ka 302 hōʻano hou?

Code 302 indicates a temporary redirection.
One of the most notable features that differentiate it from a Hoʻouna houʻo 301 ʻo ia hoʻi, ma ka hōʻike o 302 redirect, ʻaʻole i hoʻoneʻe ʻia ka ikaika o ka SEO i kahi URL hou.

google seo

ʻO kēia no ka mea i hana ʻia kēia hoʻoponopono hana i ka wā e pono ai ke hoʻoneʻe i ka ʻikepili i kahi ʻaoʻao ʻaʻole i kuhikuhi ka papa.
Pēlā i ka wā e hoʻopau ʻia ai ka hōʻano hou ʻana, ʻaʻole i nalowale ka ʻaoʻao kumu i kona kūlana ma ka ʻimi hulina a Google.
ʻOiai ʻaʻole maʻamau maoli ka ʻike iā mākou iho e pono ai ma kahi hoʻolālā 302, hiki i kēia koho ke lilo i mea maikaʻi loa i kekahi mau hihia. ʻO kēia ka mea maʻamau loa:

  • Ke hoʻomaopopo nei mākou aia kekahi manaʻo kūpono ʻole i kekahi ʻaoʻao. ʻOiai e hoʻopau i ka pilikia, hiki iā mākou ke hoʻihoʻi i ka mea hoʻohana i kekahi ʻaoʻao ʻē aʻe i makemake ʻia.
  • I ka hanana ʻana o kā mākou pūnaewele e hoʻihoʻi i kahi o nā ʻaoʻao, hiki i kēia neʻe ke kōkua iā mākou e hōʻemi i nā mea i koe.

ʻO kahi neʻe 302 kahi palapala e haʻi i ka poʻe malihini i kahi URL kikoʻī ua neʻe ʻia ka ʻaoʻao ma kahi manawa pōkole, e kuhikuhi pololei iā lākou i ka wahi hou.
I nā huaʻōlelo ʻē aʻe, hoʻoneʻe ʻia ka 302 i ka wā e noi ana nā robots Google a i ʻole nā ​​mea huli ʻē aʻe e hoʻouka i kahi ʻaoʻao kūikawā. I kēlā manawa, hoʻomaikaʻi i kēia kuhi hou, hoʻihoʻi ka mea hoahana i kahi pane maʻalahi e hōʻike ana i kahi URL hou.
Ma kēia ala ke pale ʻole ʻia ai nā hewa a me nā huhū.

He aha kahi hōʻano 302 no?

E lawelawe ana ka ʻōmaʻomaʻo 302, ʻo ia hoʻi, i kekahi mau loli ma ka ʻaoʻao ʻokoʻa i nā ʻōlelo ʻokoʻa.
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.

Hoʻouna houʻo 302

Ma keia ala, a akaulii o pūnaewele hana halihali Loaʻa ia, akā i ka manawa like, ʻaʻole i hoʻōla ʻia ka mana ma ka pae SEO o ka ʻaoʻao nui. Ke hoʻomau nei kēia i nā wā, ʻoiai ʻaʻohe mea i hoʻokaʻawale i ka mana, e like me kā mākou wehewehe mua ʻana.

ʻO HTTP 302 hōʻano hou

The most common HTTP 302 redirect example case is Google.
ʻAʻohe o ka ʻāina āu e kipa ai, inā ʻoe e kaomo nei https://www.google.com/, you will be redirected to the Google version in the language/country that corresponds to you.

google search
I kahi o Kelemānia, 302 lawe koke iā mākou https://www.google.de/ i hiki iā mākou ke ʻimi i nā ʻike i ka Kelemania.
Hoʻohana kekahi o nā ʻoihana o nā hui kūleʻa e like me Coca-Cola a i ʻole Fujitsu e hoʻohana i kēia ʻōnaehana e hoʻoneʻe hou i ka hele ʻana i kahi e manaʻo ai lākou he mea maʻalahi loa.

What causes HTTP 302 error?

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

  • Ke hoʻohana nei i 302 kuli ma ke neʻe ʻana o ka pūnaewele;
  • Ke hana nei i kahi papa 302 i ka neʻe ʻana i ka palapala;
  • Ke hoʻohana nei i kahi hana 302 i ka wā e hoʻololi ai ka protocol pūnaewele;
  • Ke kūkulu nei i ka 302 redigects ʻoiai ke loli nei ka pae.

ʻAʻole kuhikuhi ʻia ka loiloi HTML 302 i ka wā e noi ʻia ai ke ʻano o ke noi kumu i ka noi ʻana o ka URL i hele aku ai - ka laʻana, ka neʻe ʻana i ka URL o kahi kuhikuhi kuhikuhi i hoʻohana i ke ʻano POST no kahi manawa kikoʻī.
ʻAʻole ʻoe e hoʻohana i ke code status 302 inā makemake ʻoe e hoʻololi i ka SEO-paona ma ka URL hele aku.

How to identify HTTP 302 error?

ʻO ka hōʻoia ʻana ka 301 a me 302 hōʻano hou pololei ke hoʻonohonoho ʻana Maʻalahi loa.
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.

aupuni inoa
Eia kekahi koho ʻē aʻe - e noi ana no ka nānā ʻana i ke code pane a ka server i nā lawelawe pūnaewele, no ka laʻana, http://example.com/e_redirect/.
Inā ʻoe e hoʻokū i kahi ʻōmaʻomaʻo pololei, ma hope o ke komo ʻana i ka inoa inoa inoa, e ʻike ʻoe i ke code pane 301 a i ʻole 302. Ma muli o ke ʻano o ke kuli ʻoi ʻia āu i hoʻolālā ai e loaʻa mua.
ʻO kekahi mau lawelawe i hoʻohui ʻia i ke code i hāʻawi ʻia e ka server ma hope o ka hoʻoiho ʻana, a ma ʻaneʻi hoʻokahi wale nō nā koho kūpono - 200 ʻĀ.

How to fix HTTP 302 error?

Kaila 1: E nānā i ka hoʻonohonoho hoʻonohonoho

E hoʻohana paha ka noi ma luna o ka mea hoʻohana i hoʻohana i kekahi o kēia mau polokalamu ʻoihana pūnaewele maʻamau, Nginx a Apache paha. Hoʻopili kēia mau mea hoʻoponopono pūnaewele ʻelua ma mua o ka 84 ka pakeneka o ka papahana pūnaewele pūnaewele puni honua!
Therefore, the first step in determining the 302 response code is checking the mandatory redirect instructions in the webserver program configuration file.

No ka Pūnaewele Pūnaewele Apache

Laki 1: E wehe i ka faila .htaccess ma ke kikowaena

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.

cPanel Kōnae Pule
Inā loaʻa kāu polokalamu i ka host ka mea i hoʻokipa ʻia, i loaʻa iā ʻoe kou inoa inoa i ka pili ʻana o ka host, he laʻana. I kēia hihia, ʻo ka maʻamau, ʻo ka papa kuhikuhi o ke kumu noi e kau ʻia ma ke ala.
/home/<username>/public_html/path, thus the .htaccess file is located at /home/<username>/public_html/.htaccess.

KaʻAnuʻu 2: E ʻimi i nā ʻōkuhi mod_rewrite

I ka manawa e loaʻa ai ʻoe .htaccess faile, wehe iā ia ma ke kākau inoa-a loaʻa i ka laina e hoʻohana ana i nā kuhikuhi Rew RewXXX no ka modache Apache mod_rewrite.

mod_rewrite
Eia naʻe, ʻo ka manaʻo nui e kuhikuhi i ka kuhikuhi a RewriteCond i kahi huaʻōlelo i hoʻohālikelike ʻia i ka URL i hoʻopaʻa ʻia. Ke noi nei kahi malihini i ka URL e pili ana i kahi pūnaewele, ʻo ke alakaʻi RewriteRule e kuhikuhi ana i kekahi o nā ʻōlelo kuhikuhi RewriteCond maoli e hoʻohuli hou i ka noi no ke URL pili.
No ka laʻana, he hui maʻalahi me ka hui pū ʻana o RewriteRule a me RewriteCond e hoʻopiha i nā koi a pau o example.com, akā e hoʻoheheʻe iki kahi lōneʻeneʻe kūʻokoʻa i loko o ka URI kūʻokoʻa wale nō - example.com:

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

E nānā i kahi kikoʻī hou ma lalo o RewriteRule, e hōʻike ana me kahi pāʻali pane he 302, e hōʻike ana i ka mākaʻi ʻōpala he ʻano hana iki kēia.

KaʻAnuʻu 3: E hoʻokū i nā kuhikuhi i ka faila .htaccess
# BEGIN WordPress RewriteEngine I RewriteBase / RewriteRule ^ index \ .php $ - [L] RewriteCond% {REQUEST_FILENAME}! -F RewriteCond% {REQUEST_FILENAME}! -D RewriteRule. /index.php [L] # KOA WordPress

No laila, inā e kiʻi ʻoe i kahi kuhikuhi RewriteRule maʻamau a i ʻole RewriteCond kuhikuhi i kāu faila .htaccess i kū pono ʻole iā ia, e hoʻāʻo e hana pōkole iā lākou (prefixed me #) a hoʻihoʻi hou i ka pūnaewele e nānā inā ua hoʻoholo ʻia ka pilikia.

No ka pūnaewele pūnaewele Nginx

Ka ʻahiki 1: E wehe i ka faila nginx.conf

kaʻina hoʻopio
Inā e holo ana kāu pūnaewele pūnaewele ma Nginx, pono ʻoe e ʻimi no ka faila ʻokoʻa loa o ka hoʻonohonoho. Ua kuhikuhi ʻia kēia faila ma ka ngxx.conf ma ke kahaha a loaʻa i kekahi o nā kuhikuhi maʻamau i kau ʻia ma lalo nei:

/ usr / ʻona / nginx / conf, / etc. / nginx or, / usr / local / etc / nginx.

Ka Hana 2: E kākau hou i nā ʻōkuʻi ma ka file nginx.conf

Ma hope o ka nānā ʻana, wehe i ka faila nginx.conf i kāu kākau huaʻōlelo a loaʻa i nā kuhikuhi kuhikuhi i pili i kahi kuhikuhi.

HTTP 302 error: 301 scheme
ʻO kēia, he kuhikuhi poloka mākaʻikaʻi (i hoʻolaha ʻia i kahi ʻōlelo o ka ʻōlelo) e hoʻonohonoho i ka pelekikena kikowaena ma ka hana ʻana i kahi hoʻoneʻe lima pōkole mai abc.com a kahi paʻa -abc.com:

hoʻokipa {hoʻolohe 80; hoʻolohe 443 ssl; server_name www.abc.com; kākau hou ^ / $ http://www.temporary-abc.com redirect; }

Hoʻokumu ʻo Nginx i nā kuhikuhi pono e like me ka Apache RewriteRule a
RewriteCond no ka mea maʻamau lākou i ka hana ʻimi i nā hana e pili ana i ka hana maʻalahi.

Ka Hana 3: E nānā i ke kulekele hoʻololi o ka faila nginx.conf

I kekahi hihia, e nānā i ka file nginx.conf no ke kulana hoʻololi ae he loaʻa kahi kikowaena ʻōwili (ʻoi aku ka code code pane pane kūʻokoʻa 301).

HTTP 302 error: nginx parameters
Eʻoluʻolu e nānā i kekahi mau mea ʻē aʻe ma mua o kou hoʻomaka ʻana i ka mea kikowaena e nānā ai inā hoʻoholo ʻia ka pilikia.

Ka Waihona 2: Huli i nā lako ʻike loina ʻole

ʻO ka ʻōlelo kikoʻī o ka RFC no ka HTTP 1.0 e ʻōlelo ana ʻo ka pahuhopu o kahi code pane "302 Found" i manaʻo ʻia e hōʻike e hana ka mea kūʻai aku i kahi hana hoʻokaʻawale.

HTTP 302 error: device risk
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.
No ka hoʻopau ʻana i kēia pilikia, ua hoʻihoʻi ka palapala kiko kikoʻī o ka RFC HTTP 1.1 i nā code pane 303, kahi 307 hou ka hoʻokaʻawale ʻana, kahi ala e hiki ai ke mālama i ka POST-to-GET a i ʻole, kūlohelohe i pane ʻole.

Ka Waihona 3: Ka hoʻomaʻemaʻe ʻana i nā lāʻau

Aneane kokoke nā hale kūʻai pūnaewele āpau i hoʻopaʻa i ka waihona. Aia ka loiloi a ka noi palapala noi i ka mōʻaukala noi, e like me nā ʻaoʻao, ka noi a me nā pilina, i loaʻa mai ka waihona i hāʻawi ʻia, a pēlā aku.

HTTP 302 error: clean the logs
Hoʻopili ʻia nā lāʻau koʻikoʻi i nā polokalamu i kēia manawa e holo nei i nā polokalamu a ʻike mau i ka ʻike e pili ana i ke kūlana a me ke olakino o nā lawelawe i hoʻopili ʻia, a me ka ʻikepili hoʻi e pili ana i ka kikowaena.
Google record [PLATFORM_NAME] ma CMS a i ʻole hoʻohana iā [PROGRAMMING_LANGUAGE] e hoʻopaʻa inoa a hoʻopaʻa inoa i [OPERATING_SYSTEM] i ka wā e hoʻolilo ai i ka noi hana maʻamau no ka ʻike hou aʻe e kiʻi ai kēia mau mooolelo.

Kaila 4: E hoʻoponopono i ka helu noi

Ma ka hihia, ua pau nā hana i ʻōlelo ʻia ma luna nei, hiki ke loaʻa paha ka pilikia i ke code hoʻohana o ka noi i hoʻokau i ka pilikia.

HTTP 302 error: web browser
E ho'āʻo e hoʻoholo i ke kumu o ka pilikia ma o ka huli lima ʻana i ka noi a hoʻopaʻa ʻia iā ia i ka faila server a me nā faila log.
He manaʻo maikaʻi e kope i ka noi holoʻokoʻa i kāu kamepiula hoʻomohala kaiāulu a hoʻoili ma waena o ia mea e ʻike pololei i nā mea e tupu nei i ka neʻe 302 a ʻike i ke ʻano no kēlā me kēia noi.

HTTP 302 Error: Conclusion

ʻO ka mea hope loa, e like me kāu i ʻike ai, ʻaʻole pono mākou e makaʻu i nā ʻāpana e pili ana i ka hala o ka HTTP 302. Ma waho o ke hele ʻana aku, kahi ala maikaʻi loa ia e pale ʻole ai i ka nalo ʻana i kā mākou pūnaewele me nā loli like ʻole e kū mai nei i nā makahiki.
I hope that, after reading this article, you will not get chills every time about how do I fix the 302 moved temporarily error.
Inā makemake ʻoe e hāʻawi i mea kōkua i ka pou a i ʻole inā he nīnau a makemake paha ʻoe e hāʻawi i kou manaʻo, mai kānalua e ʻōlelo i lalo!