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
Hello!
We faced such issue: in the production environment we can't enable Debug logging without full excluding CURLLogger because credentials are printed either.
CURLLogger is important, because it shows the real request to ArangoDB and we can't use it.
Maybe we can configure this behavior in some way?
If not I think it would be good to have this opportunity, because enabling debug for CURLLogger can be impossible by security reasons.
The text was updated successfully, but these errors were encountered:
Hello!
We faced such issue: in the production environment we can't enable Debug logging without full excluding CURLLogger because credentials are printed either.
CURLLogger is important, because it shows the real request to ArangoDB and we can't use it.
https://github.com/arangodb/arangodb-java-driver/blob/master/src/main/java/com/arangodb/internal/http/CURLLogger.java#L63
Maybe we can configure this behavior in some way?
If not I think it would be good to have this opportunity, because enabling debug for CURLLogger can be impossible by security reasons.
The text was updated successfully, but these errors were encountered: