Closed execveat closed 2 years ago
The randomic port allows to load, even if there was an half-unload or in case you run more than one Burp instance, I would not change that.
On the other hand, the predictable port number makes continuous testing easier when you might close and open Burp many times (e.g. over multiple days).
InQL saves data on queries, tabs, etc in Local Storage, but it only works over the same Origin.
We could server both use-cases by creating a new setting. Would that suit you and would you prefer it being 0 (auto) or 5612 by default?
GraphiQL wasn't working anymore, so I ported the new version. This change includes a slight reworking on how the interface gets incorporated as I'd like to port GraphQL Voyager in a similar manner.
This pull-request also incorporates CORS headers as the lack of those headers was blocking load of GraphiQL in Chrome.