Comments (5)
dhubler
commented on June 16, 2024
FreeCONF doesn't support XML
https://freeconf.org/docs/reference/compliance/rfcs/
Curious, is this just for compliance? My impression was there is little
practical reason to support this, only theoretical. I'm not sure how hard
this would be to support.
If you pass anything but application/yang-data+json you get regular JSON
and not namespaces per RFC7951 much like how gnmi supports both
https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md#231-json-and-json_ietf
…On Thu, Apr 13, 2023 at 7:21 AM Patrick Dumais ***@***.***> wrote:
When doing a POST with content-type "application/yang-data+json", the
restconf server responds with a correctly formated response that conforms
to our yang model.
But if the request is made with application/yang-data+xml. then the
response is send as application/yang-data+json, but with the top level
attribute stripped out.
—
Reply to this email directly, view it on GitHub
<#31>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACA7VW5JQ2FZ2NJAAWL63XA7OTLANCNFSM6AAAAAAW456K2I>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
from restconf.
pdumais
commented on June 16, 2024
If you pass anything but application/yang-data+json you get regular JSON
This means that issue #29 should not get resolved then. I'll take a look at the RFC. Do you remember where you saw that?
from restconf.
pdumais
commented on June 16, 2024
actually, let me rephrase the issue.
When a request is made with content-type yang-data+xml, it is ok to respond with yang-data+json.
When when receiving the response, I expect it to be the same regardless. In our case, we are missing the top level node of the json document.
from restconf.
dhubler
commented on June 16, 2024
Today we have:
When
Accept: yang-data+json
Expect
JSON IETF7951
When
Accept: anything else
Get
JSON
You want:
When
Accept: yang-data+json or yang-data+xml
Expect
JSON IETF7951
When
Accept: anything else
Get
JSON
If so, I kinda feel if the ask is for xml, we should error, not return JSON
(IETF7951 or otherwise)
…On Thu, Apr 13, 2023 at 7:48 AM Patrick Dumais ***@***.***> wrote:
actually, let me rephrase the issue.
When a request is made with content-type yang-data+xml, it is ok to
respond with yang-data+json.
When when receiving the response, I expect it to be the same regardless.
In our case, we are missing the top level node of the json document.
—
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACA7UJXR57HL47WHWU67TXA7RZ7ANCNFSM6AAAAAAW456K2I>
.
You are receiving this because you commented.Message ID:
***@***.***>
from restconf.
pdumais
commented on June 16, 2024
Our problem was that we needed to explicitely set OnlyStrictCompliance to true. But then XML is not working at all
Our client is sending content-type and accept to yang-data+xml
In that case, it should instead return a 415.
We're gonna have to request XML support. We can talk about this through another channel
** message edited
from restconf.
Related Issues (20)
- Support dynamic addition of client CAs HOT 11
- Support the media types in RFC
- Add error reporting as per section 7.1 from RFC-8040 HOT 3
- Client - *nodeutil.Basic - OnChoose not implemented -device-tool.endpoint
- Support verifying that a leaf of type empty is present or not in ActionRequest.Input HOT 6
- Unable to go get restconf HOT 2
- Server replies with 200 OK while setting error HOT 9
- Set content-type to application/yang-data+json as specified in RFC8040 HOT 2
- typedef empty not found HOT 3
- Feature request: Support XMLparsing HOT 1
- Feature request: Support XML output HOT 7
- ServeHTTP in server is not using Request context HOT 2
- Restconf server automatically opens a HTTP server HOT 1
- RPC operations in wrong location HOT 4
- RPC inputs are not supported as per RFC HOT 1
- Duplicate/Bad test for restconf server? HOT 1
- GET request to '/' gets redirected to '/web/` and might not be valid
- notification event formatting HOT 2
- json object keys are not fully qualified w/module prefix HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from restconf.