Failing Thing Model Helper

[danielpeintner]

coming from #1253 but seems to be a general issue with the CI.

Somehow on the CI servers it reports 500 error instead of 404

   2 failing

  1) tests to verify the Thing Model Helper
       should fail on unavailable linked ThingModel - http:

      AssertionError: expected promise to be rejected with an error including 'http status code not 200 but 404 for …' but got 'http status code not 200 but 500 for …'
      + expected - actual

      -http status code not 200 but 500 for http://example.com/models/colored-lamp-1.0.0.tm.jsonld
      +http status code not 200 but 404 for http://example.com/models/colored-lamp-1.0.0.tm.jsonld
      
  

  2) tests to verify the Thing Model Helper
       should fail on unavailable linked ThingModel - https:

      AssertionError: expected promise to be rejected with an error including 'https status code not 200 but 404 for…' but got 'https status code not 200 but 500 for…'
      + expected - actual

      -https status code not 200 but 500 for https://example.com/models/colored-lamp-1.0.0.tm.jsonld
      +https status code not 200 but 404 for https://example.com/models/colored-lamp-1.0.0.tm.jsonld

[relu91]

It seems that somebody registered the example.com domain and put a real server behind it. It could be that previously it would correctly answer 404 now for an unknown reason it fires a 500.

[danielpeintner]

I tried with a REST client and it still fires 404 on my machine.. but it seems the CI setup does differently. Hence I would soften a bit the check as done in #1255