PH-
Welcome to PHCorner Forums! Sign up for free to unlock full access and exclusive privileges, including:
- Asking questions about computer and mobile issues
- Discovering internet tips for your mobile network and computer
❓ Help Laging status 302 ang injector
- Thread starter jtultra
- Start date
Tama po yan, nasa timpla po ng payload http injector settings yan. Kahit pa yung http status code ng inyong bughost ay 200, 302... Nasa combinasyon po yan kung ano ang laman ng payload parameters, kaya yung resulta ay maiiba.
Bigyan ko kayo ng sample scenario: (Yung nasa kanan po, yung initial http status check ng bughost, at yung nasa kaliwa po ay epekto ng connection depende sa sample payload settings, proxy, etc...)
Payload settings: Normal, Post, Front Inject, Online Host, Forward Host, Keep Alive
Payload settings: Normal, CONNECT, Normal Inject, Online Host, Forward Host, Keep Alive
(Note: Yung 128.199.100.124 ay test usage po ng actual remote IP as bughost sa http injector, for experiment lang po he he.)
Kung stucked yung ginawa ninyo sa 302 error, may mali kung saan sa settings ninyo.
Ang isang solution po sa error sa taas ay ito:
Yang payload setting na yan ay user-friendly, bukod sa iba pang kadahilanan dahil halos lahat ng proxies ay pasok sa GET request. Many many thanks po kay Mang Tano
!
Ang isa pa pong importance ng http status code checks ay para makita yung response sa redirects - http and https. Gamitin ninyo yung proxychecker ni Proxifier to verify. Yan yung dapat ninyong malaman para gamitin yung tamang proxy na merong ganyang kakayahan.
Sa tingin ko, malinaw na po siguro sa inyo ito - at least for now.
Bigyan ko kayo ng sample scenario: (Yung nasa kanan po, yung initial http status check ng bughost, at yung nasa kaliwa po ay epekto ng connection depende sa sample payload settings, proxy, etc...)
Payload settings: Normal, Post, Front Inject, Online Host, Forward Host, Keep Alive
Code:
fb.me (302-200 status, 1 redirect) incomplete connection (stuck at SSH first key exchange only) 302 error-payload
g.co (200 status) 411-payload (successful 200 connection)
128.199.100.124 (400 status) 400-payload (successful 200 connection)Payload settings: Normal, CONNECT, Normal Inject, Online Host, Forward Host, Keep Alive
Code:
g.co (200 status) 200-payload (successful 200 connection)
fb.me (302-200 status, 1 redirect) 200-payload (successful 200 connection)
128.199.100.124 (400 status) 200-payload (successful 200 connection)(Note: Yung 128.199.100.124 ay test usage po ng actual remote IP as bughost sa http injector, for experiment lang po he he.)
Kung stucked yung ginawa ninyo sa 302 error, may mali kung saan sa settings ninyo.
Ang isang solution po sa error sa taas ay ito:
Code:
Payload settings: Normal, Get, Front Inject, Online Host, Forward Host, Keep Alive
fb.me (302-200 status, 1 redirect) 200-payload (successful 200 connection)Yang payload setting na yan ay user-friendly, bukod sa iba pang kadahilanan dahil halos lahat ng proxies ay pasok sa GET request. Many many thanks po kay Mang Tano
!Ang isa pa pong importance ng http status code checks ay para makita yung response sa redirects - http and https. Gamitin ninyo yung proxychecker ni Proxifier to verify. Yan yung dapat ninyong malaman para gamitin yung tamang proxy na merong ganyang kakayahan.
Sa tingin ko, malinaw na po siguro sa inyo ito - at least for now.
- Status