Thug riochdaire den neach-dèiligidh againn, aig a bheil stac tagraidh a ’fuireach san sgòth bho Microsoft (Azure), aghaidh air duilgheadas: o chionn ghoirid, thòisich cuid de dh’ iarrtasan bho chuid de luchd-dèiligidh às an Roinn Eòrpa a’ tighinn gu crìch le mearachd 400 (). Tha a h-uile tagradh sgrìobhte ann an .NET, air a chleachdadh ann an Kubernetes ...
Is e aon de na tagraidhean an API, tro bheil an trafaic gu lèir a ’tighinn aig a’ cheann thall. Bidh am frithealaiche HTTP ag èisteachd ris an trafaic seo , air a rèiteachadh leis an neach-dèiligidh .NET agus air aoigheachd ann am pod. Le debugging, bha sinn fortanach leis an fhaireachdainn gu robh neach-cleachdaidh sònraichte ann a bha gu cunbhalach ag ath-riochdachadh an duilgheadas. Ach, bha a h-uile dad iom-fhillte leis an t-sreath trafaic:
Bha a’ mhearachd ann an Ingress a’ coimhead mar seo:
{
"number_fields":{
"status":400,
"request_time":0.001,
"bytes_sent":465,
"upstream_response_time":0,
"upstream_retries":0,
"bytes_received":2328
},
"stream":"stdout",
"string_fields":{
"ingress":"app",
"protocol":"HTTP/1.1",
"request_id":"f9ab8540407208a119463975afda90bc",
"path":"/api/sign-in",
"nginx_upstream_status":"400",
"service":"app",
"namespace":"production",
"location":"/front",
"scheme":"https",
"method":"POST",
"nginx_upstream_response_time":"0.000",
"nginx_upstream_bytes_received":"120",
"vhost":"api.app.example.com",
"host":"api.app.example.com",
"user":"",
"address":"83.41.81.250",
"nginx_upstream_addr":"10.240.0.110:80",
"referrer":"https://api.app.example.com/auth/login?long_encrypted_header",
"service_port":"http",
"user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36",
"time":"2019-03-06T18:29:16+00:00",
"content_kind":"cache-headers-not-present",
"request_query":""
},
"timestamp":"2019-03-06 18:29:16",
"labels":{
"app":"nginx",
"pod-template-generation":"6",
"controller-revision-hash":"1682636041"
},
"namespace":"kube-nginx-ingress",
"nsec":6726612,
"source":"kubernetes",
"host":"k8s-node-55555-0",
"pod_name":"nginx-v2hcb",
"container_name":"nginx",
"boolean_fields":{}
}Aig an aon àm, thug Kestrel seachad:
HTTP/1.1 400 Bad Request
Connection: close
Date: Wed, 06 Mar 2019 12:34:20 GMT
Server: Kestrel
Content-Length: 0Eadhon leis a’ bhriathrachas as motha, bha mearachd Kestrel gu math mòr beagan fiosrachaidh feumail:
{
"number_fields":{"ThreadId":76},
"stream":"stdout",
"string_fields":{
"EventId":"{"Id"=>17, "Name"=>"ConnectionBadRequest"}",
"SourceContext":"Microsoft.AspNetCore.Server.Kestrel",
"ConnectionId":"0HLL2VJSST5KV",
"@mt":"Connection id "{ConnectionId}" bad request data: "{message}"",
"@t":"2019-03-07T13:06:48.1449083Z",
"@x":"Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Malformed request: invalid headers.n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1Connection.TryParseRequest(ReadResult result, Boolean& endConnection)n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.<ProcessRequestsAsync>d__185`1.MoveNext()",
"message":"Malformed request: invalid headers."
},
"timestamp":"2019-03-07 13:06:48",
"labels":{
"pod-template-hash":"2368795483",
"service":"app"
},
"namespace":"production",
"nsec":145341848,
"source":"kubernetes",
"host":"k8s-node-55555-1",
"pod_name":"app-67bdcf98d7-mhktx",
"container_name":"app",
"boolean_fields":{}
}Bhiodh e coltach nach cuidich ach tcpdump an duilgheadas seo fhuasgladh... ach nì mi a-rithist mun t-sreath trafaic:
Rannsachadh
Gu follaiseach, tha e nas fheàrr èisteachd ri trafaic air a' phuing shònraichte sin, far a bheil Kubernetes air pod a chuir a-steach: bidh meud an dump cho mòr is gum bi e comasach rudeigin a lorg gu math luath co-dhiù. Agus gu dearbh, nuair a chaidh a sgrùdadh, chaidh am frèam a leanas a thoirt fa-near:
GET /back/user HTTP/1.1
Host: api.app.example.com
X-Request-ID: 27ceb14972da8c21a8f92904b3eff1e5
X-Real-IP: 83.41.81.250
X-Forwarded-For: 83.41.81.250
X-Forwarded-Host: api.app.example.com
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Original-URI: /front/back/user
X-Scheme: https
X-Original-Forwarded-For: 83.41.81.250
X-Nginx-Geo-Client-Country: Spain
X-Nginx-Geo-Client-City: M.laga
Accept-Encoding: gzip
CF-IPCountry: ES
CF-RAY: 4b345cfd1c4ac691-MAD
CF-Visitor: {"scheme":"https"}
pragma: no-cache
cache-control: no-cache
accept: application/json, text/plain, */*
origin: https://app.example.com
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36
referer: https://app.example.com/auth/login
accept-language: en-US,en;q=0.9,en-GB;q=0.8,pl;q=0.7
cookie: many_encrypted_cookies; .AspNetCore.Identity.Application=something_encrypted;
CF-Connecting-IP: 83.41.81.250
True-Client-IP: 83.41.81.250
CDN-Loop: cloudflare
HTTP/1.1 400 Bad Request
Connection: close
Date: Wed, 06 Mar 2019 12:34:20 GMT
Server: Kestrel
Content-Length: 0
Às deidh sgrùdadh nas dlùithe air an dump, chaidh am facal a thoirt fa-near M.laga. Tha e furasta a chreidsinn nach eil baile-mòr M.laga anns an Spàinn (ach tha ). A’ gabhail ris a’ bheachd seo, thug sinn sùil air na configs Ingress, far am faca sinn am fear a chaidh a chuir a-steach o chionn mìos (air iarrtas an neach-dèiligidh) criomag “gun chron”.:
ingress.kubernetes.io/configuration-snippet: |
proxy_set_header X-Nginx-Geo-Client-Country $geoip_country_name;
proxy_set_header X-Nginx-Geo-Client-City $geoip_city;Às deidh dha na cinn-cinn sin a chuir air adhart, dh’ fhàs a h-uile dad gu math! (Cha b’ fhada gus an robh e soilleir nach robh feum aig an tagradh fhèin air na cinn-cinn sin tuilleadh.)
A-nis leig dhuinn sùil a thoirt air an duilgheadas san fharsaingeachd. Faodar ath-riochdachadh gu furasta taobh a-staigh an tagraidh le bhith a’ dèanamh iarrtas telnet gu localhost:80:
GET /back/user HTTP/1.1
Host: api.app.example.com
cache-control: no-cache
accept: application/json, text/plain, */*
origin: https://app.example.com
Cookie: test=Desiree
... tilleadh 401 Unauthorized, mar a bhiodh dùil. Dè thachras ma nì sinn:
GET /back/user HTTP/1.1
Host: api.app.example.com
cache-control: no-cache
accept: application/json, text/plain, */*
origin: https://app.example.com
Cookie: test=Désirée?
Tillidh e 400 Bad request - ann an loga an tagraidh gheibh sinn mearachd air a bheil sinn eòlach mu thràth:
{
"@t":"2019-03-31T12:59:54.3746446Z",
"@mt":"Connection id "{ConnectionId}" bad request data: "{message}"",
"@x":"Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Malformed request: invalid headers.n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1Connection.TryParseRequest(ReadResult result, Boolean& endConnection)n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.<ProcessRequestsAsync>d__185`1.MoveNext()",
"ConnectionId":"0HLLLR1J974L9",
"message":"Malformed request: invalid headers.",
"EventId":{
"Id":17,
"Name":"ConnectionBadRequest"
},
"SourceContext":"Microsoft.AspNetCore.Server.Kestrel",
"ThreadId":71
}Builean
Gu sònraichte Kestrel pròiseas cinn-cinn HTTP gu ceart leis na caractaran ceart ann an UTF-8, a tha ann an ainmean àireamh meadhanach mòr de bhailtean-mòra.
Is e feart a bharrachd sa chùis againn nach eil an neach-dèiligidh an-dràsta an dùil buileachadh Kestrel san tagradh atharrachadh. Ach, tha cùisean ann an AspNetCore fhèin (, ) tha iad ag ràdh nach cuidich seo...
Gus geàrr-chunntas: chan eil an nota tuilleadh mu na duilgheadasan sònraichte aig Kestrel no UTF-8 (ann an 2019?!), ach mu dheidhinn sin mothachadh agus sgrùdadh cunbhalach Bheir a h-uile ceum a bheir thu fhad ‘s a tha thu a’ lorg dhuilgheadasan toradh nas luaithe no nas fhaide air adhart. Beannachd leat
PS
Leugh cuideachd air ar blog:
- «";
- «";
- «";
- «";
- «".
Source: www.habr.com