make above pytests reproducible by using a mock server that responds with those different failure categories

[kuefmz]

No description provided.

[Akshat1000Sharma]

can you please give details about this issue

[JJ-Author]

the task is to create a web server or environment that emulates everything that can get wrong when trying to access an ontology / web document
from connection error, time outs, http error codes, redirection loops and such.
start with the other issues you asked for first please.

[Akshat1000Sharma]

Thanks for replying, i will be sure to finish the other issues first before getting back on this

[deepak-dobbala]

I am a bit confused about what the issue is can you provide a description

[JJ-Author]

1. provide a deterministic http(s) hazard emulator
   so add a new component ( configure/extend existing approaches or potentially create a new one if that is easier) to the project that realizes a webserver that can simulate many kinds of "hazards" that can occur when trying to access an ontology ( or in general a web document) via HTTP and HTTPS

• transport (tcp) connection errors
• invalid tls certificaed or (expired, non-matching dns, etc.)
• delaying repsonse sucht that client timed outs are triggered
• returning all kinds of http error codes
• creating redirection loops
• returning wrong mimetypes
• returning empty body or inaccurate bytesize compared to reported content size

2. extend the pytests that additionally instead of just using the test IRI in
   non_archivo_test_IRIs.tsv and archivo_test_IRIs.tsv (which could change everytime )
   to controllable deterministic IRIs that go to the hazard component and create a consistent hazard over time.