You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmmm... but this only works in local mode, right? I mean, go-ftw will be reading local files, in the local host (or mounted filesystem) to know where to find the logs.
Hmmm... but this only works in local mode, right? I mean, go-ftw will be reading local files, in the local host (or mounted filesystem) to know where to find the logs.
Yes, only in local mode. I would try to use different rule sets for different VHOST's.
I want to test a custom rule set with a specific pre-configured vhost, which listens on localhost (127.0.0.1).
I added
Host
header to each test, eg:The test request is sent with the specified header, but when
go-ftw
sends the marker requests before and after it, they has "localhost".So the markers' logs are written to the original log, but the test result is written into the vhost's own log (if there is).
It would be nice if the marker requests also use the
Host
header like the test itself.Workaround: use the same error.log for specific vhost as the default.
The text was updated successfully, but these errors were encountered: