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
I am trying to get the network log and gnerating a HAR file with browsermobproxy and I am not able to get the response content data, ie the content data has size 0 always.
for example when I go to this url: #626
mobproxy HAR file :
"content": {"size": 0,"mimeType": "image/jpeg","comment": "" }
Notice the content size is 0 but other details are fetching alright. I have 110 records similar to this in the HAR file all having content size as 0. When I generated the HAR from the chrome dev tools, I can see the data of the response (as byte46) and the content size is not 0. What am I doing wrong, please help!
My main aim to get the HAR file is to get a certain blob from LinkedIn from a network call which cannot be directly accessed because of the security. I have to see the response content data using mobproxy, I have tried adding SSL certifications This is the my selenium and mobproxy code block
I am trying to get the network log and gnerating a HAR file with browsermobproxy and I am not able to get the response content data, ie the content data has size 0 always.
for example when I go to this url: #626
mobproxy HAR file :
"content": {"size": 0,"mimeType": "image/jpeg","comment": "" }
Notice the content size is 0 but other details are fetching alright. I have 110 records similar to this in the HAR file all having content size as 0. When I generated the HAR from the chrome dev tools, I can see the data of the response (as byte46) and the content size is not 0. What am I doing wrong, please help!
My main aim to get the HAR file is to get a certain blob from LinkedIn from a network call which cannot be directly accessed because of the security. I have to see the response content data using mobproxy, I have tried adding SSL certifications This is the my selenium and mobproxy code block
The text was updated successfully, but these errors were encountered: