Closed Molinware closed 3 hours ago
Asking just in case: are you sure it is ok to publicly expose this many names/folders/identifiers/strings from your project?
Duplicate of:
Asking just in case: are you sure it is ok to publicly expose this many names/folders/identifiers/strings from your project?
I don't belive it would generate any problem for us, but I've removed the screenshots. If more info is necessary please let me know.
It should be fixed in https://github.com/OData/odata.net/pull/3081. @WanjohiSammy OData hasn't released a new AspNetCore.OData nuget package to consume that changes. of course, OData team should release a new version of AspNetCore.OData.
@Molinware Before the new version, can you manually update the OData.Core dependency version to 9.1.0 in your project to see whether the fix in ODL 9.1.0 works?
Yes, can you point me to where can I download it? Asking because in the nuget package manager the last version is 8.1.0:
Yes, can you point me to where can I download it? Asking because in the nuget package manager the last version is 8.1.0:
@Molinware 8.1.0
is the one. Please update OData.Core to 8.1.0
and test.
Confirmed, working with AspNetCore.Odata 9.0.0 and OData.Core to 8.1.0.
Assemblies affected ASP.NET Core OData 9.0.0
Describe the bug Calling the /$metadata more than one time generates error.
Reproduce steps
Extra Information:
Data Model Not important for this issue.
EDM (CSDL) Model
Request/Response HTTP/1.1 GET http://localhost:5900/Pesquisa/$metadata No status code response.
Expected behavior Return the metadata XML correctly as in the first call.
Additional context