Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clicking Compile does nothing at all ! #6

Open
minanagehsalalma opened this issue May 17, 2022 · 4 comments
Open

Clicking Compile does nothing at all ! #6

minanagehsalalma opened this issue May 17, 2022 · 4 comments

Comments

@minanagehsalalma
Copy link

as the title says when i click compile nothing happens

my script is

print("whydoesn'tthinsworrrrk")

@stavinski
Copy link
Contributor

Compile does not execute the script, it simply checks/caches the Python code so that it can be executed in the request/response pipeline.

In order to test the script you will need to have the script enabled and make some requests such as through the proxy or using repeater, you should then see the output printed.

@minanagehsalalma
Copy link
Author

@stavinski hmmm , but why can't it just output in the extender output tab?

Also how can i use this to access websockets response data ?

@stavinski
Copy link
Contributor

Not sure I understand, it will output in the extender output tab when the script is executed as part of the request/response pipeline, basically the same as if you had written an extension and hooked into callbacks.registerHttpListener(self) and put your code in the processHttpMessage method.

I don't believe that the Burp Extender API has support for websockets at present but I could be wrong (it's not something I have had to implement), it would probably require someone from PortSwigger to confirm if this is the case.

@minanagehsalalma
Copy link
Author

i see thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants