Skip to content
This repository has been archived by the owner on May 1, 2020. It is now read-only.

deprecated access to motus API v1.0 #434

Open
denislepage opened this issue Jan 25, 2019 · 0 comments
Open

deprecated access to motus API v1.0 #434

denislepage opened this issue Jan 25, 2019 · 0 comments
Assignees

Comments

@denislepage
Copy link
Collaborator

We have retired some older views in our database yesterday, and noticed that the API v1.0 was still being accessed, and some of those calls are now failing.

After a bit of digging, I found that they are originating from 131.162.131.200 (sensorgnome.org)

Here's a cleansed log entry from yesterday, before we made the change:

131.162.131.200 - - [24/Jan/2019:10:54:08 -0500] "GET /data/api/v1.0/searchtags.jsp?json=%7B%22serno%22%3A%22SG-0815BBBK1352%22%2C%22hash%22%3A%22[XXXXX]%22%2C%22date%22%3A%2220190124155359%22%2C%22fmt%22%3A%22json%22%2C%22login%22%3A%22john%22%2C%22pword%22%3A%22[XXXXX]%22%2C%22projectID%22%3Anull%2C%22tsStart%22%3Anull%2C%22tsEnd%22%3Anull%2C%22searchMode%22%3A%22startsBetween%22%2C%22defaultLifespan%22%3A90%2C%22lifespanBuffer%22%3A1.5%2C%22regStart%22%3Anull%2C%22regEnd%22%3Anull%2C%22mfgID%22%3Anull%7D HTTP/1.1" 200 12590411

Can those calls easily be switched over? They are presumably part of the connected receiver processing still happening on the old server? We can restore the API 1.0 for now if needed, but it would be good to entirely retire it soon.

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

No branches or pull requests

2 participants