M. Ángel Jimeno
M. Ángel Jimeno
Hi @bsysop it definitely makes sense. Yeah, the Go server I used to test this issue only replied with a 200 to /path but not /path/. Don't have access to...
Stale. Closing this as I rarely use ffuf nowadays. 😄
Doable by adding a couple of flags and updating `TLSClientConfig` attribute of the HTTP Transport in use.
Hi @SanderWind, That's how Go's HTTP Client works. Here you can find its Transport docs: https://cs.opensource.google/go/go/+/refs/tags/go1.17.8:src/net/http/transport.go;l=182-190 ```go // DisableCompression, if true, prevents the Transport from // requesting compression with an...
> So, if I understand correctly, the Go HTTP Client does NOT uncompress automatically the response when a raw request in fuff (read as "user") contains the Accept-Encoding header? That's...
That information wasn't present in this issue before, @SanderWind. As a hot-fix I propose you configure ffuf to use burp/caido as an upstream proxy and add the header there via...
Missed it, sorry about that! @SanderWind 🙈
This seems to be working as intended. Created the following server: ```go package main import ( "log" "net/http" ) func home() http.HandlerFunc { return func(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK)...
@Mzack9999 maybe https://github.com/hktalent/scan4all/tree/main/projectdiscovery/nuclei_Yaml is the new path for it?
@alchu4n could you pleas repeat the same steps but using the `-debug` flag? This might be working as expected. ``` -debug display request/response content in cli ```