Re: OPS timeouts on 6 and 7 January 2018
Posted: Wed Jan 10, 2018 9:19 pm
Confirmed!
The JSON raw response containing the access token now lacks one space at the bold underscored site:
....
"token_type": "BearerToken",
"issued_at": "1515610432202",
"client_id": "EvBooYJ6AwZna6ocokeGTfGRL6l2RQiz",
"access_token": "osmQKWOFAAkaAOqB2Xdk7TUzzxyI",
"application_name": "889c06e1-0bc2-483e-8f63-98fc386301fc",
"scope": "core",
"expires_in": "1199",
....
As the consequence the starting character of the token was not parsed anymore. The access tokens now work again, after correcting the code for the lost space. Who at the EPO programmer staff hat this idea to change this without telling anyone? This presumably caused a lot of unnecessary work for many users including me!
But the problem with the timeouts still persists.
mike_k43
The JSON raw response containing the access token now lacks one space at the bold underscored site:
....
"token_type": "BearerToken",
"issued_at": "1515610432202",
"client_id": "EvBooYJ6AwZna6ocokeGTfGRL6l2RQiz",
"access_token": "osmQKWOFAAkaAOqB2Xdk7TUzzxyI",
"application_name": "889c06e1-0bc2-483e-8f63-98fc386301fc",
"scope": "core",
"expires_in": "1199",
....
As the consequence the starting character of the token was not parsed anymore. The access tokens now work again, after correcting the code for the lost space. Who at the EPO programmer staff hat this idea to change this without telling anyone? This presumably caused a lot of unnecessary work for many users including me!
But the problem with the timeouts still persists.
mike_k43