You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The site uses multipart/form-data as the encoding:
In Firefox, the raw multipart encoded data ends up as a string in text in the HAR:
In Chrome, meanwhile, both textandparams are populated in the HAR:
In params, the file I uploaded is "helpfully" replaced with (binary), in text, it appears to be missing entirely. In fact, as far as I can tell, the uploaded file isn't included anywhere in the HAR. o.o
And indeed, I can't seem to find a way to get to it in the Chrome dev tools, either:
So, don't use Chrome to generate HAR files if you want them to actually contain everything you've uploaded, I guess? Phenomenal stuff.
And, more importantly for us, the mitmproxy HAR dump script. I only had an example for application/x-www-form-urlencoded lying around. In that case, it populates both params and text:
In
unhar()
, we are currently assuming that a HAR can only hold a request body inrequest.postData.text
:TrackHAR/src/common/request.ts
Line 45 in b219141
That is not true. It can also have POST params in
request.postData.params
(which we are currently just ignoring):http://www.softwareishard.com/blog/har-12-spec/#postData
The text was updated successfully, but these errors were encountered: