Perhaps you should do a test with Postman or Curl or some other utility first and then see if you can get it to work with RPG.
I always do that before attempting to create a call in RPG to make sure I can get the service in question to work.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------
message: 1
date: Wed, 22 Oct 2025 14:36:42 -0700
from: x y <xy6581@xxxxxxxxx>
subject: Re: [WEB400] "HTTP/1.1 403 Forbidden" error from HTTPAPIR4
Then I remain mystified as to the authorization mechanism because I'm using
the same URL's at other customers' locations and the vendor does not do any
IP filtering.
On Sat, Oct 18, 2025 at 10:24?PM Scott Klement <web400@xxxxxxxxxxxxxxxx>
wrote:
This isn't an SSL problem, not related to certificates.
You sent a URL that the server says you don't have access to. ("Access
forbidden" or just "Forbidden")
On 10/17/25 9:17 AM, x y wrote:
An app using HTTPAPIR4 runs without issue on multiple systems, including
systems delivered new from IBM. It's a straightforward SOAP app--I
deploy
the code and it works.
However, it's not working with a new customer's existing system--I get
the
dreaded "HTTP/1.1 403 Forbidden" returned from HTTPAPIR4. This Canadian
customer does not have other SOAP or REST apps running and they're very
security-conscious, so I suspect they've blocked themselves from getting
into the internet for port 80/443 calls.
Their system may not have a certificate--is the problem that simple?
And I told them this would be an easy install...thank you for your help!
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/web400.
midrange.com
