Repository navigation
Origin data handling #163
Description
Activity
If some host bits are set, it definitely came from a not-standards-compliant source or suffered a form of corruption, which would make me wonder "what else is wrong with this file?" From this perspective rejection seems safest, ultimately forces the operator to manually take a look if the cache purges itself based on the expiry keyword.
hmm the only thing is.. what do we wanna do then when we reject the new file? we can just use the old shit or maybe even tear down rtr sessions. i actually think we should tear down rtr sessions tbh, but it does give me aggressive feelings.
Originates from comment by @job in #156 (comment)