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

Services from https://services.odata.org/v4/odata/ respond with header OData-Version: 4.0; instead of 4.0 #216

Open
boghyon opened this issue Sep 25, 2022 · 7 comments

Comments

@boghyon
Copy link

boghyon commented Sep 25, 2022

  1. Go to https://services.odata.org/v4/odata/
  2. Click on any of the mentioned services. E.g. https://services.odata.org/Experimental/Northwind/Northwind.svc/
  3. The service's response header OData-Version has the value 4.0; which contains unexpectedly a semicolon and thus causes issues in the client. It should be without the semicolon: 4.0.

Is the extra semicolon OData V4 compliant? If not, it should be removed.
TripPin on the other hand does not have the issue.

@AnupamSAP
Copy link

I am also facing the same issue. Is it working for you?

@boghyon
Copy link
Author

boghyon commented Apr 13, 2023

I am also facing the same issue

With which service? The ones listed in https://services.odata.org/v4/odata/?


@ralfhandl Is the OData-Version response header value 4.0; syntactically allowed? Because the additional semicolon breaks the client OData implementation.

@ralfhandl
Copy link

The OData ABNF does not allow a trailing semicolon, see https://github.com/oasis-tcs/odata-abnf/blob/d1b3373f73408d1dd177198057cc12940a30c6c8/abnf/odata-abnf-construction-rules.txt#L1077.

@ravish-garg
Copy link

Is there any progress on this?

@mydoghasfleas
Copy link

Hi, at this point in time, the response from the v4 service at https://services.odata.org/v4/odata/ is still broken; it still returns "4.0;" in the "Odata-Version" header.
Is there anyone that can fix this?

@aleferr3ira
Copy link

Hi, any updates on this? I'm also facing the same issue.

@niteshtdcv
Copy link

Hi Team,

is there any workaround on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants