[Fiware-tech-help] FIWARE-NGSI v2 Swagger Specification - omissions for working with subscriptions

Taz Lodder taz at chalmers.se
Thu Nov 11 13:29:00 CET 2021


Hi (yet again)! Sorry as you can tell I'm working extensively with FIWARE lately.


I get an empty set when trying to request a subscription list as documented here https://swagger.lab.fiware.org/#/Subscriptions/List%20Subscriptions:


$ curl -i --insecure -X GET 'https://localhost/v2/subscriptions' -H 'X-Auth-token: 577...82b'
HTTP/2 200
server: nginx/1.18.0 (Ubuntu)
date: Thu, 11 Nov 2021 12:26:22 GMT
content-type: application/json
content-length: 2
fiware-correlator: 94aaac08-42ea-11ec-a8c9-0242ac1d0006
strict-transport-security: max-age=63072000

[]


After some scratching my head, I decided to try adding the fiware-servicepath and fiware-service headers and hey-presto results!


Maybe useful to add to the Swagger spec for the future? I think I was caught out with the same issue some months ago too.


Taz

Chalmers University of Technology
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20211111/b93d87bb/attachment.html>


More information about the Fiware-tech-help mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy