Closed trumpy81 closed 7 years ago
Log entries in the log is:
`Sep 12, 2017 19:55:19.443 [4300] DEBUG - EventSource: Failure in ParseHeader: HTTP/1.1 404 Not Found
Content-Type: text/html; charset=utf-8
Date: Tue, 12 Sep 2017 09:55:19 GMT
Server: nginx
Vary: Origin
X-Request-Id: 2c71d209-9da3-4c83-9ca7-2fcca42a207d
X-Runtime: 0.003206
Content-Length: 1118
Connection: keep-alive
<!DOCTYPE html>
` So we are showing it as it is! When that's said, I suggest you ask Plex why they log such an entryNo, you are missing the rest of the file. It abruptly ends at the HTML tag and only shows those few lines before it.
There are two instances of that error in the log. ;)
Also, there is no warning to open the file in a text editor.
I have no idea why Plex adds that to the log, I don't even see any issues when that is logged, so it seems rather pointless to me.
Sorry, but we phrase what's in the logs.... In order to color it etc....
So if Plex due to a bug suddenly drops html code in the log, we can't do anything about that
Actually, I've reopened this one....
@creoludifico
Frontend have an issue here, and tries to get:
@ukdtom Yes, that is exactly what we don't want (Javascript/Html rendering from the logs). I'll check
Perfect
Environment
Error shown
No warning is shown to open the file in a text editor.
Steps to reproduce
Expected behaviour
Actual behaviour
Additional Info
Observed in Chrome, Edge and FireFox.
Checklist
Log file being viewed: Plex Media Server.log.zip
Screenshot of issue: