It’s not a new feature, it’s been there for a while
HAR files generated by WebService requests are not that big compared with files generated by capturing the traffic for WebUI tests with the mobproxy workaround.
For WebService, one HAR contain a single request. The biggest part of it is … the response content.
For WebUI, you capture lot of additional data.
e.g for my above case, is just ~ 4K in size:
[ibus@ibus-t14 ~]$ ls /tmp/Katalon/Test\ Cases/Api\ call\ test/20230608_111141/requests/main/ -alh
total 8.0K
drwxr-xr-x. 2 ibus ibus 60 Jun 8 11:11 .
drwxr-xr-x. 3 ibus ibus 60 Jun 8 11:11 ..
-rw-r--r--. 1 ibus ibus 4.3K Jun 8 11:11 0.har
for a response of:
"content" : {
"size" : 996,
HAR files captured with mobproxy for WebUI may be also imported with DevTools and analyzed in the Network tab:
I dont have such file at hand so cannot confirm. For files generated by webservice does not work.
Another nice toy is the HAR Analyzer provided by Google, this one loads fine also files generated by WebService requests:
