-
Hi,
I'm trying to integrate Scorpio Broker with FIWARE IoT Agent for Sigfox Protocol. In the device provisioning the NGSI-LD entity is created successfully. But when I am trying to send measurement…
-
When you enable CORS for all origins request to .../v2/ work with CORS but request to .../ngsi-ld/v1/ do not work
-
**log from fiware-orion**
`time=Monday 28 Jun 15:07:28 2021.213Z | lvl=TMP | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=orionldMhdConnectionInit.cpp[494]:orionldMhd…
-
Add the FIWARE-Correlator header to notifications, if present in the original request.This is not an NGSI.-LD thing,
it dates back to NGSIv2, but, that's OK.
Some day we'll discuss this feature in E…
-
Following example returns
`{
"type": "https://uri.etsi.org/ngsi-ld/errors/BadRequestData",
"title": "Invalid value for Subscription::q",
"detail": "forbidden characters in String Filter"
}…
-
Orion based on NGSI v2 supports custom payload inside notification field. For example:
```
“notification”:
"httpCustom": {
"url": "http://foo.com/entity/${id}"…
-
## I wish
To find OpenAPI V3 spec files
## Instead
I just find Swagger V2 spec files ;)
## Notes
if you need support in the conversion, I could help!
-
-
- Site: [https://api.nonfunctionaltest.can4l.com](https://api.nonfunctionaltest.can4l.com)
**New Alerts**
- **Cross-Domain Misconfiguration** [10098] total: 1:
- [https://api.nonfunctionalte…
-
- Site: [https://api.nonfunctionaltest.can4l.com](https://api.nonfunctionaltest.can4l.com)
**New Alerts**
- **Cross-Domain Misconfiguration** [10098] total: 1:
- [https://api.nonfunctionalte…