"apidump --out" creates empty folder / no har file? about observability-cli HOT 3 CLOSED

Hi, Christian. I think there are a couple things going on here, and the tool could be clearer about the results (or lack thereof).

apidump will work for outbound traffic as well if you include a filter; you can do --filter "port 443" or --filter "port 80"

However, because the connection is encrypted with HTTPS, the tool cannot see which URLs are being accessed. A combination that worked for me is:

sudo bin/akita apidump -c 'curl -I -L http://api.github.com/users/torvalds/events/public' --out ./dumpdir -u root --filter "port 80"

But it is not very interesting because all it shows is the redirection to HTTPS.

from observability-cli.

Sorry for the noise. I was mistaken that apidump should work both for in- and outbound traffic. Dumping inbound traffic works fine. #close

from observability-cli.

hi @mgritter,

ah, thanks a lot, now it makes sense.
Just hacked together a little proxy server (really bad code, but just to try) that listens on unencrypted http and translates http:// urls to https:// urls while proxying. Now I seem to be able to do:

$ jetis
starting proxy server on localhost:8888 ...

and

sudo akita apidump -c 'curl --proxy http://localhost:8888 http://api.github.com/users/torvalds/events/public' --out . -u root --filter "port 8888"

and I'm getting a 400 KB .har file with promising content. 🎉

(Maybe as a feature idea ... a built-in proxy in akita apidump might be useful, so you don't have to hook up another proxy tool like charles to record outgoing requests?)

from observability-cli.