I have an application token. According to documentation
If you are throttled for any reason, you will receive a status code
429 response.
I have received no errors that I am being throttled. Sending requests from other servers are accepted just not the one that has been working fine up until today. What needs to be done to unblock my server and/or prevent it from reoccurring?
Related
I'm not really an EWS user, just trying to help debug a mailing application that stopped working last year.
We get an error message when trying to send() that the connection was forcibly closed. Reading up on the issue it seems like a lot of folks are saying it's a TLS version problem.
Someone here think it's because we are using Basic Authentication (instead of Modern Authentication with OAuth 2.0). We don't see any issues directly related to authentication.
By still using Basic Authentication, can that cause the connection closed issue when we try to execute the send() method?
No a connection being forcibly closed is most likely either TLS, bad ip reputation (eg a lot of spam/fraud coming from a certain IP that has been blacklisted) or your sending a message with a very large attachment in a single request. If it was a Basic Authentication disabled issue you would get a 401 error, if its was that EWS had been disabled (eg via set-casMailbox) you could get a 403.
I am facing request timeout issue with Azure API App. When the request size is fairly large (more than 120 kb). I encounter a timeout issue and the request doesn't reach the app. On disabling client auth the same request works seamlessly.
Try setting up the App Service setting to enable clientCert. Then try calling the API to see if I get a 401 response. After that I would try adding the certificate to the request and see if I can pick it up in my API-endpoint
https://learn.microsoft.com/en-us/azure/app-service/app-service-web-configure-tls-mutual-auth
I have already gone through multiple links before posting and it is not a repeat question.I am not pretty sure that i should post it here or on server fault.
I am trying to configure the SMTP email task but running into error mentioned below.
System.Net.WebException: Unable to connect to the remote server
System.Net.Sockets.SocketException:An attempt was made to access a socket in a way forbidden by its access permissions ipaddress:25
I also tried to verify using powershell, if the SMTP is fine and below are the results:
Using Send-mailmessage : It is working really fine
Using Net.Mail.SmtpClient : I could send email to organization email ids but not outside.
Can someone help me understand where exactly the problem could be.
The problem was Antivirus was blocking the requests from SSIS but was allowing the powershell requests.
I'm loading a cross-origin script that requires a username/password using HTTP Basic Access Authentication.
I'm not concerned with the security of the username/password. My code:
<script src="http://user:password#example.com/script.js"></script>
This works fine in most cases. However, if the credentials are incorrect, an authentication dialog pops up.
I would like to abort the loading of the script if the credentials are wrong instead of presenting the authentication dialog to the user. Ideally a JavaScript function would be triggered as well to alert that something has gone wrong.
Is this possible, and how would it be done?
I think this would fall on the server-side configuration.
Instead of sending a HTTP 401 Not Authorized with WWW-Authenticate header, the server should respond with a different status code, perhaps 403 Forbidden
The problem is that when a 401 is sent to the browser, the browser interprets that as a login requirement, prompting the user. If it receives another error status (i.e. 403) it will simply error out (which can be caught by a JavaScript function)
I have C++ Win32 app that uses HttpSendRequest to request some URL (via https). It worked OK earlier; but then errors ERROR_INTERNET_INCORRECT_HANDLE_STATE began happen. Why these ones? Any ideas?
I stumbled across something very similar recently. It suggests that your HttpOpenRequest has either failed or not yet completed, or during the HttpSendRequest() call the connection died for some reason (SSL handshake problems, Certificate problems, or just simple TCP connection problems).
I specifically saw the problem when developing an app using the asynchronous WinINET process, and my calls to HttpQueryInfo and InternetReadFile were failing with that return code.
In my case, I wasn't correctly waiting for the async notifications from HttpSendRequest to be received before calling the other methods, and also in cases where I wasn't correctly dealing with failures during the connection.
I know its a year late, but hopefully that helps.
It seems trivial but,
did you have flag INTERNET_FLAG_SECURE in making HttpOpenRequest?
as described in:
http://support.microsoft.com/kb/168151
For I myself was stuck here for hours until I found above knowledge base entry.
I got the same error on Windows XP for HTTPS connection (all flags correct) for the HTTP2 server endpoint, I wonder if it can't properly handle HTTP2 connection or the certificate.