Opened 8 years ago

Closed 8 years ago

#930 closed enhancement (duplicate)

Force endpoint XSD validation to only use cached XSDs

Reported by: Sander Maijers Owned by: Dirk Goldhahn
Priority: major Milestone:
Component: Monitoring Version:
Keywords: Cc: b.von.st.vieth@fz-juelich.de, Dieter Van Uytvanck, teckart@informatik.uni-leipzig.de

Description

Whenever w3.org or openarchives.org has some availability problem, currently endpoints receive an Icinga notification about the CRITICAL status of their endpoint. This is confusing and annoying. Make sure that XSD validation only uses locally cached copies of the required XSD files. Of course, this was already the intention and many XSDs are already in place, but URL references to remote XSD copies keep popping up.

Change History (3)

comment:1 Changed 8 years ago by DefaultCC Plugin

Cc: teckart@informatik.uni-leipzig.de hynek@informatik.uni-leipzig.de Sander Maijers added

comment:2 Changed 8 years ago by Dieter Van Uytvanck

Cc: hynek@informatik.uni-leipzig.de Sander Maijers removed

comment:3 Changed 8 years ago by Dieter Van Uytvanck

Resolution: → duplicate
Status: new → closed

Duplicate of #905 - closing

Note: See TracTickets for help on using tickets.