Remove todo and clarify severity

NSteell · Mar 8, 2019 · 016f289 · 016f289
1 parent 1fd7bd7
commit 016f289
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/IMPLEMENTATION.md b/IMPLEMENTATION.md
@@ -311,7 +311,7 @@ Additionally, in every `/loadtracks` response, a `loadType` property is returned
 
 If the loadType is `LOAD_FAILED`, the response will contain an `exception` object with `message` and `severity` properties.
 `message` is a string detailing why the track failed to load, and is okay to display to end-users. Severity represents how common the error is.
-A severity level of `COMMON` indicates that the error is non-fatal and can usually just be ignored.
+A severity level of `COMMON` indicates that the error is non-fatal and that the issue is not from Lavalink itself.
 
 ```json
 {

diff --git a/LavalinkServer/src/main/java/lavalink/server/config/RequestAuthorizationFilter.java b/LavalinkServer/src/main/java/lavalink/server/config/RequestAuthorizationFilter.java
@@ -26,7 +26,6 @@ public RequestAuthorizationFilter(ServerConfig serverConfig) {
 
     @Override
     public boolean preHandle(HttpServletRequest request, HttpServletResponse response, Object handler) throws Exception {
-        // TODO: Log IP
         String authorization = request.getHeader("Authorization");
 
         if (authorization == null || !authorization.equals(serverConfig.getPassword())) {