Twinql: Query from Agent

gistfile1.txt

Query from Agent: POST
XHR
https://databox.me/,query [HTTP/2.0 200 OK 148ms]
Headers
POST
Response
Call Stack
throughAgent http://127.0.0.1:8081/public/app.js:65:3
runQuery http://127.0.0.1:8081/public/app.js:103:3
<anonymous>

Calls: https://github.com/dan-f/twinql/blob/master/public/app.js

--- @dieu
... When you’re using the agent, all requests are sent through a proxy-like server (the agent) 
that also handles authentication for you (using WebID-TLS delegation for now).

-- @danf
....The "query from server" button POSTs the query to a web server which then does that exact same work, 
but on your behalf, and responds back to you with the result of the query.
The other main benefit is that the client doesn't have to ingest all the graphs followed during link 
following which may be very large, even if it's only interested in a small piece of the graph

--- @danf
...  If you run it from a server, that server of course uses GETs, but you need to POST the query to that 
server for it to parse it from the body.

This is what happens when the Query from Agent button is clicked.

I was observing the call stack and how it matched with what Dan and Andrei said should happen.
And they appear to match.