wojciech.kapcia@tigase.net opened 5 months ago
|
||||||||||
Do you have any idea what requests are causing this issue? I've found following code in the source code of
That would suggest that something is sending 304 and is setting content or passing length of not Possibly, we could modify https://github.com/tigase/tigase-http-api/blob/a80837c747099682070426756cf8c8eef48c9d1e/src/main/java/tigase/http/java/DummyServletResponse.java#L307 to log stacktrace for calls causing this issue. Note: I've not observed any entries like that during normal usage of a new version, so I wonder if that is not caused by some external services sending HEAD requests. |
||||||||||
It happens on virtually all navigation (/admin, /dashboard, /). Each click/brows one generates at least 3-4 entries (probably number of requests). Though I just tried and it stopped happening... and it was happening constantly... |
||||||||||
wojciech.kapcia@tigase.net batch edited 5 months ago
|
||||||||||
wojciech.kapcia@tigase.net batch edited 5 months ago
|
||||||||||
Referenced from commit 5 months ago
|
||||||||||
Andrzej Wójcik (Tigase) changed state to 'In Progress' 5 months ago
|
||||||||||
Andrzej Wójcik (Tigase) changed state to 'In QA' 5 months ago
|
||||||||||
Referenced from commit 5 months ago
|
||||||||||
I've found cause of this issue (checking if assets/css/js files were modified) and I've applied a fix for this issue. |
||||||||||
wojciech.kapcia@tigase.net changed state to 'Closed' 4 months ago
|
Type |
Improvement
|
Priority |
Minor
|
Assignee | |
Version |
tigase-server-8.5.0
|
Target Release |
1.0
|
Sprints |
n/a
|
Customer |
n/a
|
-
tigase-server-8.5.0 Open