-
Notifications
You must be signed in to change notification settings - Fork 168
Description
Description:
When using a custom macro in Burp Suite to update cookie values on every request, the Logger++ extension fails to display the response for those requests. Instead, the Status column shows a value of -1. The macro successfully updates the cookies, and testing the macro separately confirms that the cookie values are correctly modified. However, when Logger++ logs the request after the macro modification, it does not show the expected response.
Steps To Reproduce:
Create New Session Handling Rule
- Navigate Settings > Sessions > Session handling rules
- Add a new rule
- Details tab> Rule actions > Add > use cookies from the session handling cookie jar (Leave everything as default values)
- Scope tab > Tools Scope (Select all)
- Scope tab > URL scope (Select include all URLs)
- Use tools like
dalfox or ffufproxy traffic to burp suite (To prevent browser behaviours and update cookies automatically)
dalfox.exe url https://target.com -C "__cookie=INVALID_COOKIE" --proxy "http://127.0.0.1:8080" --timeout 10000 - Ensure that the macro is triggered and the cookies are updated (Use Open Session tracer for this purpose)
- Observe the request in Logger++: note that the response is missing and the Status column shows -1.
Expected behavior:
Logger++ should log the modified request with the correct response data, and the Status column should display the appropriate HTTP status code (e.g., 200, 307, etc.) rather than -1.
Screenshots:
Modified A Request By Macro Result In Logger++:

The Same Request Log From BurpSuite Default Logger:

Version:
-
Logger++ 3.20.0 by @CoreyD97.
-
java -version
- openjdk version "23.0.1" 2024-10-15
- OpenJDK Runtime Environment (build 23.0.1+11-39)
- OpenJDK 64-Bit Server VM (build 23.0.1+11-39, mixed mode, sharing)
-
Windows 10.0.19045 Build 19045