If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity.
There are many ways to solve the "request failed: forbidden (403) error". The administrator can configure each web server so that the individual methods are either allowed or not allowed . Note 1896961 - HTTP/HTTPS Configuration for SAP NetWeaver Gateway After a bit of tinkering with configuration, I finally found a solution. The following sections describe problems that have been resolved by Service Packs for WebLogic Server 6.1. ... it may be interfering with the web page you are trying to load into your browser. For more information, see https://goo.gl/zmWq3m. I made following changes to my Realm Assign Groups: ADMIN,MEMBER and then in glassfish-web.xml,