We are noticing users with Norton antivirus aren't able to upload direct to Aws s3. There is a 403 error thrown on the s3 url. We have traced this to being very specifically Norton users only and happens in both ie and chrome
here are the console errors
request for 0
https://****.s3.amazonaws.com/****.mp4?uploads Failed to load resource: the server responded with a status of 403 (Forbidden)
custom.fineuploader-5.0.9.min.js:25 [Fine Uploader 5.0.9] POST request for 0 has failed - response code 403
custom.fineuploader-5.0.9.min.js:25 [Fine Uploader 5.0.9] Specific problem detected initiating multipart upload request for 0: 'The difference between the request time and the current time is too large.'.
custom.fineuploader-5.0.9.min.js:25 [Fine Uploader 5.0.9] Chunked upload request failed for 0, chunk 0
**** used in place of real information
The log messages (added after the question was posted) suggest that the issue is with a clock drift on the user's machine. It's not clear how this is related to Norton. If the clock on the user's machine drifts too far from the actual time, then AWS will reject the request. You'll need to be sure that the machine clock is reasonably accurate.
A similar question was asked at Fine Uploader getting "Policy expired" message sending to S3 for some.
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.
I have a web api which is deployed on IIS.
Api's are going through load test using load runner and almost on all alternative api call, getting 403 error response code, struggling to identify the issue, call is not going to the API, its returned back from IIS
I am doing bearer token authorization, somehow token which were incoming with each request were not valid, that is why the issue was occurring, to overcome this we have increased the lifetime of token to 1 hour and request load test team to generate the token once and send that token only with each request so that we can now see the proper execution time for each end point.
403 error indicates that access to the requested URL by the client is Forbidden for some reason. you need to provide detailed error message snapshot and what is the sub status code. and check that you assign this permission to the site folder:1) IIS_IUSRS,2)NETWORK SERVICE,3)IUSR
I need to upload considerable amount of videos on YouTube, so I have a c# application, upload one file each 5 minutes. The problems is, it intermittently throw "access forbidden". For example it worked for around 4 hours this morning, then it became moody again :D. Any same experience recently with YouTube API?
It's the error I receive sometimes, but not always, after successful authentication, when it tries to upload:
Google.Apis.Requests.RequestError
Access forbidden. The request may not be properly authorized. [403]
Errors [
Message[Access forbidden. The request may not be properly authorized.] Location[ - ] Reason[forbidden] Domain[youtube.common]
]
My clients report this error from time to time. They receive new::ERR_EMPTY_RESPONSE and the upload retries the maximum number, then fails. Most recent occurrence was on OSX Maverick, Chrome. It happens on Safari as well.
The problem is not widespread, it occurs on a relatively small % of clients.
Fine Uploader 5.1.3
s3.jquery.fine-uploader.js:3878
new::ERR_EMPTY_RESPONSE
s3.jquery.fine-uploader.js:29
POST request for 0 has failed - response code 0
Received an empty or invalid response from the server!
Here is a console screenshot
The issue is with your server or network. The browser complains the the preflight request is being returned with a completely empty response. This is not an issue with Fine Uploader. You'll need to examine logs on your signature server, or perhaps there are some network issues on your end or your client's end.
I'm getting the following error intermittently when invoking the custom search api from a server side setup:
HttpError 403 when requesting https://www.googleapis.com/customsearch/v1?q=John+Doe+john%40simpler.com&alt=json&cx=&key= returned "There is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your API key configuration if request from this IP or referer should be allowed.
I'm using a server api key, and have confirmed that the configured server ip address is correct. And about 50% of the time my request come back fine, too. I'm issuing the request from the server like this:
service = build("customsearch", "v1",
developerKey=api_key)
custom_search_context = <my_context>
res = service.cse().list(
q=search_query_string,
cx=custom_search_context,
).execute()
My requests per sec are well with in the configured limit of 10/sec and daily purchased limit of 5000 requests.
One more thing I noticed is that Google counts a forbidden request towards the daily limit, too.
Any pointers on why I'm being presented with the error only intermittently would be very helpful
The error can be raised when you're exceeding a request/second limit. Can you confirm that your request rate is below your configured user rate limit? It might be worth noting that the limit is enforced even if you don't explicitly provide a user value in your requests.