Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature references (HTTP status code 302) #912

Closed
Dnoack49 opened this issue Jan 20, 2023 · 3 comments
Closed

Feature references (HTTP status code 302) #912

Dnoack49 opened this issue Jan 20, 2023 · 3 comments
Labels
deployed in reference validator Solution deployed in production duplicate This issue or pull request already exists
Milestone

Comments

@Dnoack49
Copy link

Dear all,

1.) a description of the steps to reproduce your issue

We have validated the following Address-Dataset:
https://inspire.brandenburg.de/services/ad_alkis_wfs?service=WFS&version=2.0.0&request=GetFeature&Count=10&typenames=ad:Address

and received error messages, that properties reference resources that cannot be accessed (for instance: https://registry.gdi-de.org/id/de.bb.inspire.ad.alkis/AdminUnitName_12062341) - the reason is: The HTTP status code when requesting the resource is: '302'. A status code of '200' is expected.

2.) used browser and version: Firefox Browser 108.0.1 (64-Bit)

3.) a screenshot illustrating the problem
grafik

4.) the Test Report
Test run on 17 38 - 19.01.2023 with test suite Annex I - Addresses (AD).zip

5.) the name of the Test that failed :
Conformance class: Information accessibility, Adresses // Feature references//ad-ia.b.1:Address.component

Indeed the GET-Request of e.g. https://registry.gdi-de.org/id/de.bb.inspire.ad.alkis/AdminUnitName_12062
leads to a Code 302 (Found):
grafik

For us the question is:
Shouldn't the validator also expect/accept 302 as a valid return ?
This might be treated similar to the issue md sds 3.6: Coupled Resource #190

kind regards

@fabiovinci
Copy link
Collaborator

Dear @Dnoack49,

thank you for the issue, it was already solved for all the data themes (see my comment on issue 559).

The solution is already available in the staging instance, see the report for your dataset.
The only remaining errors are related to the link https://registry.gdi-de.org/id/de.bb.inspire.ad.alkis/AdminUnitName_120 which is not available.

The solution will be included in the release 2023.0 that will be released in the coming days.

@fabiovinci fabiovinci added the solved Solution developed and accepted, not yet deployed label Jan 23, 2023
@fabiovinci fabiovinci added this to the v2023.0 milestone Jan 23, 2023
@fabiovinci fabiovinci added the duplicate This issue or pull request already exists label Jan 23, 2023
@Dnoack49
Copy link
Author

Dear @fabiovinci ,
indeed it is fixed. Thank you, shall I close the issue?

@fabiovinci
Copy link
Collaborator

Thank you, @Dnoack49, for testing the solution.
We will close the issue after the release.

@fabiovinci fabiovinci added deployed in reference validator Solution deployed in production and removed solved Solution developed and accepted, not yet deployed labels Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed in reference validator Solution deployed in production duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants