Resource bug: On the Incarnation of the Word of God (Audio)
Chapter XLV of On the Incarnation of the Word of God (Audio) is broken. The media won't download. It looks like the problem is a bad link in the resource itself, becauseL
- There's no sign of a download being attempted.
- If you guess the URL, you can manually download the chapter.
- The webcache contains the following:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<title>503 Connection timed out</title>
</head>
<body>
<h1>Error 503 Connection timed out</h1>
<p>Connection timed out</p>
<h3>Guru Mediation:</h3>
<p>Details: cache-lcy1122-LCY 1495727596 289588591</p>
<hr>
<p>Varnish cache server</p>
</body>
</html>
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
-
Mark,
It looks like you had a download timeout. Can you try to delete and download the media to see if it persists? I can't reproduce this.
0 -
Deleting the file in the webcache did the trick. So it's not a resource bug.
However, Logos shouldn't have cached a file that the server returned with a 503 error. It should only cache files that have a 200 HTTP response.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark,
If you had the resource open to that chapter and not the overview it will automatically cache it.
0 -
Yes, but it shouldn't cache a download error. That makes no sense. It should only cache a valid download.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
Yes, but it shouldn't cache a download error. That makes no sense. It should only cache a valid download.
Mark,
Your right it shouldn't have cached a failed download. I'll try to replicate the situation and see what is happening.
0 -
Philana R. Crouch said:
Your right it shouldn't have cached a failed download. I'll try to replicate the situation and see what is happening.
This same thing just happened to me again. It's frustrating that 503 errors get cached, and its not straightforward to delete single files from the cache, so most users would have to delete all downloaded media just to be able to get one wrongly cached file to play.
I'm attaching the log this time. Four files failed. The first two were nt314evansaudio_75.mp3 and nt314evansaudio_79.mp3. They're on lines 13053 and 13092. I'm attaching all four files and my log. You'll be able to work out the other two failures from the log.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Hi Mark,
Thank you for updating this thread with additional logs. I'll try to reproduce this issue.
0 -
Mark,
I just wanted to let you know we're still working on trying to reproduce it. I'll report back here with any updates.
0
