dperezBM

Dear @alitka, Thank you for the services that you provide us. We tested them and we were not able to reproduce the "is not an HTTP or HTTPS URL" error....

Dear @AntoRot, We are still investigating this problem. We ran the bunch of metadata that you provided us two times on the staging instance. On the first run, we received...

Dear @alitka, Thank you for your feedback. We have also tested all seven metadata files that you provide us against the production and staging instance and we only received one...

Dear @alitka, Since you commented on your results, we have tested the metadata included on the report on several occasions (production, staging and localhost instances) and we always get “passed”...

Dear @alitka, Thank you for your reports. To continue analyzing this behaviour on the validator, could you please share with us the full reports and the metadata you tested with...

Dear @alitka, Thank you for your response. We will keep investigating the services that you provide us. Sorry for my misexplanation about the reports. I was referring to the reports...

Dear users, We have updated our [staging instance](http://staging-inspire-validator.eu-west-1.elasticbeanstalk.com/etf-webapp/) adding new log messages to analyze this issue in more detail. These messages will help us to collect the URL and the...

Dear @enricoboldrini, @MartinePaepen, @felnne, With the intention to resume this problem, could you please confirm that the error is still occurring? And if so, could you please send us the...

Dear @mpleic, In order to replicate what is causing this error, could you please send us the data you are using? If the information contained in this data is sensitive,...

Dear @JohannaOtt , Thank you for your message. As we commented on issue #622, we have tested your service directly against [OGC Validator](https://cite.opengeospatial.org/teamengine/) and the results are the same that...