Closed iBicha closed 3 weeks ago
Not really fond in doing that since we already have a set of tools to make it easier to talk to YouTube API: https://github.com/iv-org/youtube-utils
Not really fond in doing that since we already have a set of tools to make it easier to talk to YouTube API: https://github.com/iv-org/youtube-utils
This is what I prefer (and use) to debug issues - I prefer to see exactly what Invidious is doing and when etc I don't feel strongly about merging this PR, just sharing what I find productive for myself
@iBicha I recommend you to use proxychains
with mitmproxy
. That is what I use to debug requests on Invidious like I did here: https://github.com/iv-org/invidious/issues/5033
@iBicha I recommend you to use
proxychains
withmitmproxy
. That is what I use to debug requests on Invidious like I did here: #5033
Now you can use the http_proxy feature directly with mitmproxy: https://github.com/iv-org/invidious/blob/2e3a7ad044b3e37d15d0c87bb33cb85d2d04424f/config/config.example.yml#L181-L185
Closing the PR since the purpose was to share my approach. I like copying a curl command, run and dump response into a json file, then iterate on the command while diffing the response. Tweak header and payload to get innertube to return different things. This is a simple approach, doesn't require other tools, nor hooking up a proxy. Different tools for different things I guess. Feel free to repurpose this if it's ever useful
This makes invidious prints requests it makes as curl commands. For example, when visting the trending page, the following curl command would be printed:
This is useful for a few things: