Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Under Consideration
Workspace Domino Designer
Categories LotusScript
Created by Guest
Created on May 17, 2019

More User-Friendly Error Messages for NotesHTTPRequest

I've encountered a number of error codes for NotesHTTPRequest.Post(), all of which have the description "user-defined error". I haven't locked down the cause of one, but they are indeed errors of my own cause. But the lack of a helpful description makes it harder to track them down. Maybe it's because the general use case is calling non-Domino HTTP endpoints and the response from Domino is unexpected, maybe it's just that the descriptions of the causes haven't been put in the error handling part.

4844 appears to be because of lack of access to the Domino database I'm calling.

4840 was because I was posting JSON but not setting the content type header.

4846 is another I've had. I am dynamically setting the hostname and internet domain name in IDMA when the server database is opened on the server, and that generally works when called from local replicas. It's possible that there was a problem with the values stored on the occasions it was failing, I'm not sure.

More developer-friendly error messages would be helpful.

  • Attach files
  • Guest
    Reply
    |
    May 26, 2023

    If the request will be blocked because the user needs to authenticate to a proxy - it silently fails and there is no sign why a request fails. There is no error message.

    Well - the user cannot authenticate to that proxy, because a login dialog ist not implemented.