mirror of
https://github.com/Dispatcharr/Dispatcharr.git
synced 2026-07-21 01:05:30 +00:00
ea09fd0a84
Some XC servers run PHP with display_errors off, so a timestamp shape their parser rejects comes back as a hard HTTP 500 instead of a 200 with inline PHP warning text. The candidate-format cascade treated any 5xx as decisive and stopped, so catch-up never reached the timestamp shape that works on those servers and failed outright on them. Only short-circuit on genuinely decisive, ban-sensitive statuses (401/403/406 and 3xx redirects — a 302 is the first sign of an XC ban); treat 5xx like 400/404 and try the next candidate shape. Add regression tests for "500 then success" and "all candidates 500". |
||
|---|---|---|
| .. | ||
| accounts | ||
| api | ||
| backups | ||
| channels | ||
| connect | ||
| dashboard | ||
| epg | ||
| hdhr | ||
| m3u | ||
| output | ||
| plugins | ||
| proxy | ||
| timeshift | ||
| vod | ||