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

logging proxy #162

Closed
michielbdejong opened this issue Jan 6, 2025 · 4 comments
Closed

logging proxy #162

michielbdejong opened this issue Jan 6, 2025 · 4 comments

Comments

@michielbdejong
Copy link
Member

It would be nice for some use cases to have the option to run ocm-test-suite tests with a logging proxy (logging both request and response) in front of for instance each Nextcloud server.

@michielbdejong
Copy link
Member Author

Maybe I can inspect it in the docker network with something like https://husobee.github.io/http/tcpdump/docker/2016/11/30/troubleshooting-http-docker-tcpdump.html (although I guess that would not work with us due to https?)

@michielbdejong
Copy link
Member Author

michielbdejong added a commit that referenced this issue Jan 6, 2025
@michielbdejong
Copy link
Member Author

Oh, jolly! It works! docker exec -it nextcloud1.docker tail -f /etc/apache2/forensic.log

@michielbdejong
Copy link
Member Author

No POST bodies included though:

$ docker exec -it nextcloud2.docker tail -f /etc/apache2/forensic.log
+251:677bf1a8:0|GET /ocm-provider/ HTTP/1.1|Host:nextcloud2.docker|User-Agent:Nextcloud Server Crawler|Accept-Encoding:gzip
-251:677bf1a8:0
+252:677bf1a8:0|POST /ocm/shares HTTP/1.1|Host:nextcloud2.docker|content-type:application/json|User-Agent:Nextcloud Server Crawler|Accept-Encoding:gzip|Content-Length:451
-252:677bf1a8:0

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

No branches or pull requests

1 participant