-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
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. |
@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 ? |
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 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. |
i see thanks |
as the title says when i click compile nothing happens
my script is
print("whydoesn'tthinsworrrrk")
The text was updated successfully, but these errors were encountered: