Toxiproxy na iya zama a gaban proxy na HTTP

Toxiproxy na tura rafin TCP zuwa wani upstream da aka saita, kuma yana iya lalata wannan rafi. Amma HTTP control API ɗinsa ba ya mai da mai sauraron zirga-zirgar ya zama HTTP forward proxy.

Ga SDK da aka saita don amfani da proxy na HTTP, wani forward proxy da ke akwai zai iya zama a bayansa:

SDK → Toxiproxy 127.0.0.1:7890 → HTTP proxy 127.0.0.1:8888 → S3:443

Saita mai sauraron Toxiproxy a kan 7890 tare da 127.0.0.1:8888 a matsayin upstream ɗinsa. Ka nuna saitin proxy na HTTP na SDK zuwa http://127.0.0.1:7890. Mai sauraron yana tura buƙatar CONNECT ta SDK; proxy na HTTP yana fassara CONNECT kuma yana buɗe ramin manufa.

Waɗannan adiresoshin loopback suna ɗauka cewa duk sassan gida uku suna raba sararin suna na cibiyar sadarwa ɗaya. Sassan da ke cikin kwantena suna buƙatar adiresoshin da za a iya isa daga nasu sararin suna.

Wannan tsari yana canza hanyar daga abokin ciniki zuwa forward proxy. Ba ya maye gurbin TLS na manufa ko tabbatar da sabis. Lokacin da kake kimanta wata matsala da aka saka, ka lissafa sake ƙoƙarin SDK daban: aikin da ya warke na iya ɓoye wani yunƙuri da ya gaza a baya.