After upgrading [ckeditor] from 3.6.2 to **4.11.0
**
Flush API stopped working,
Flush API : https://help.cke-cs.com/api/v5/docs#tag/Collaboration/paths/%5C~1collaborations%5C~1%7Bdocument_id%7D/delete
I updated the end-points but when I am opening the document in collaborative mode and same time calling the flush API it says Some users are still connected to this collaboration session. We cannot flush it.
There is a force flag also we can send this force=true in the query parameter but when I am adding force=true in query params, Then Flush API gives an Invalid Signature response message with a 401 status code.
Can anyone help here please?
To flush the collaborative editing session forcefully.
Related
I want to reproduce a bug, these are the conditions :
GetStreamingEvents request should fail and preferably get 500 error from office365/exchange
The Resync request to send GetStreamingEvents periodically should keep failing.
Here is what I have tried so far :
I have tried to remove X-AnchorMailbox header and not send any Impersonation header but my syncing still works and GetStreamingEvents is a success.
On Exchange I moved users from one Database to another and Streaming events failed for a while till migration was in progress but it succeeded eventually.
Tried disabling Admin mailbox on exchange but that too didn't lead to any error.
Of course I tried to hardcode exchange's response but this hack is not 100% reliable.
I have Exchange2019 (acting as office365). I just want to lose my subscriptions somehow through Streaming notification mechanism of EWS. Please help me in this - what can I tweak on exchange or in my request to get streaming event failure.
We do have a kendo scheduler bound to a remote data source.
The transport configuration of this scheduler's data source is done using remote urls (for CRUD), and this works perfectly,
On the server side, we make a lot of checks. So if some requirements are missing, Create, Update or event Destroy operations wouldn't pass and user will be shown the meaningful error.
The problem we're facing now is like the following :
For the Destroy action, what kind of response should we send back (from the server) to the scheduler component (in the browser on the client side ) to prevent removal of events in the UI?
We've tried :
Sending back HTTP 500 status code
Putting an error field in the response and linking it to the schema.error configuration
But events are still removed from the UI, nevertheless the error event is fired. We even use this event to notify errors to end used.
Thank you.
I'm using Sentry to track all the errors on our production server, and I was wondering if it was possible to remove some sensitive data from the error logs :
For instance, I throw an error if a HTTP call to an API is failing. Sadly, I need to give the API access token as a query parameter of the request, and it is displayed in the error logs, in this format :
http
GET https://api.url?accessToken=abcdefg&otherparam=bar [400]
16:25:11
Can I hide or remove this accessToken ? It does not change between calls, so even setting it as an option somewhere so that it could be hidden from other people checking the Sentry logs would be alright.
While doing performance testing for Oracle Application, facing the Insufficient Privilege error on submitting one of the form from Jmeter. There is no issue manually in application not any error in debug logs. This is happening only from Jmeter. Have checked with Fiddler no requests are getting missed and also all the correlations are in place.
JMeter error :
You have insufficient privileges for the current operation. Please contact your System Administrator.
Most probably you're simply not getting logged in. Double check the following:
HTTP Cookie Manager is added to your Test Plan. In some cases you will need to add CookieManager.check.cookies=false line to user.properties file or amend Cookie Policy to something less-restrictive, i.e. netscape. Check out HTTP Cookie Manager Advanced Usage - A Guide
Make sure that you perform correlation of dynamic request parameters. Pay attention to literally everything as parameters may be present as a part of the URL, or it may be a HTTP Header
Run your test with 1 user and monitor the request and response details using View Results Tree listener. Check Response Data tab for each request to ensure that your test is doing what it is supposed to be doing
Make sure to compare the requests originating from JMeter and from the real browser, normally if you're sending the same requests - you should be receiving the same responses. Pay attention to redirects
For DELETE APIs, if we hit the API with invalid data, the API responds with proper error message. If we use the same HTTP connection object to hit another API, the request fails.
This issue is not seen for Create or Update APIs. Also if the Delete request is sent with valid data, then using the same HTTP connection object for next request works fine.
Please note that this behavior has implications for connection pooling in client applications, and we were just wondering if its known issue and if there is any available workaround.