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

bug with -output option (windows) #324

Open
badrelmers opened this issue Jul 14, 2023 · 1 comment
Open

bug with -output option (windows) #324

badrelmers opened this issue Jul 14, 2023 · 1 comment
Labels
investigation investigation Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@badrelmers
Copy link

Proxify version:

v0.0.9

Current Behavior:

-output should dump all the traffic into separate files with request followed by the response
but when I run

proxify.exe -http-addr 127.0.0.1:18080  -output logss

I get empty files
image

and a folder is created in %TEMP% (D:\Users\badr\AppData\Local\Temp) every time I start proxify, but those folders do not get deleted when I kill proxify
image

Expected Behavior:

-output should dump all the traffic into separate files with request followed by the response not empty files

and proxify should gave us a flag to control the location of the folders created in %TEMP% or at least delete those folders when proxify exit.

all this happens in win 7 64

@badrelmers badrelmers added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jul 14, 2023
@Cyb3rR3ap3r
Copy link

Cyb3rR3ap3r commented Jul 22, 2023

I can confirm I am having the same issue running on Windows 11 with traffic being sent to proxy from Chromium 114.0.5735.110.
This happens when I leave the default output directory to .\logs or I change it.

Another interesting finding is if I curl -x http://127.0.0.1:8888 google.com then I get the correct output, so I'm thinking maybe it is something with browsers.

I then tested with:
Chrome 114.0.5735.199: Same issue
Firefox 115.0.2: Works as expected!!

So maybe it has something to do with Chrome? Chrome to my knowledge doesn't have a built in proxy engine and uses the systems proxy settings so maybe that has something to do with it?

Hope this information helps.

@ehsandeep ehsandeep added the investigation investigation label Oct 11, 2023
@ehsandeep ehsandeep changed the title bug in -output flag bug with -output option (windows) Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigation investigation Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

3 participants