-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsuccessful callback to https://..... due to HTTP status code 401 #7
Comments
|
tnx for the response. this is my code where my mvc application calls Revalee service
public JsonResult RevaleeTest(string customer_no)
1.) Is the callback to an http: or an https: URL? 2a.) What is the hostname and port of the MVC application? 2.b) Is it running on the same computer as the Revalee Service? 3.) Does your local firewall/proxy software allow the Revalee Service to issue an outbound connection on that callback port? How can I allow the Revalee Service to outbound connection? 4.) Does your MVC application accept anonymous (public) connections to the callback URL? 5.) Does your MVC controller action allow the POST method to the callback URL? |
i Set the outbound connection on the Revalee Service and allow the port 92 and 65369 but still 401 status displayed in the logs |
|
1.) Yes, It works properly. A few question
I dont understand why authorization key is required. |
You assign a secret key so that you can ensure the callback action is only called by your pre-authorized callback requests. Callback validation is automatically performed if you add the [CallbackAction] attribute to the callback method or use the following line programmatically:
|
ok but why 401 status still displayed on the logs? |
It is ok if I remove the revalee tag in the web.config? |
You can remove the |
Sir, I have been setup the revalee service in my computer and also I used MVC C# Appllication to send request to Revalee, but when I visit the logs of my computer, it shows Unable to callback to https://..... due to HTTP status code 401.
The text was updated successfully, but these errors were encountered: