cloud proxy 403

  • Resolved donbowman

    (@donbowman)


    1 year, 1 month ago

    So i am trying the cloud proxy feature. I have set this to ‘REST API’, and a namespace/endpoint.

    I am getting 403 returned from the upstream. Printing this out by modifying the php, i see the below returned from cloudfront.

    I don’t see anywhere where one would enter any authz info, how may i try the feature?

    $url = https://api.nelioabtesting.com/v1/site/645937a1-456c-47c6-960f-f34c0c8d5689/event?e=W3siaWQiOiJjNjc2ZDY3YS02MWE0LTRjYjktODhhYS0xMWQyMjY0ZTQ4OTciLCJraW5kIjoidmlzaXQiLCJleHBlcmltZW50IjozMTUxNzIzLCJ0eXBlIjoicmVndWxhciIsImFsdGVybmF0aXZlIjowLCJzZWdtZW50cyI6WzBdLCJ0aW1lem9uZSI6IiswMDowMCIsInRpbWVzdGFtcCI6IjIwMjQtMDItMTdUMTY6MzE6MTcuODI0WiJ9XQ=&a=645937a1-456c-47c6-960f-f34c0c8d5689
 
[headers] => WpOrg\Requests\Utility\CaseInsensitiveDictionary Object
     (
         [data:protected] => Array
             (
                 [content-type] => application/json
                 [content-length] => 82
                 [date] => Sat, 17 Feb 2024 16:31:20 GMT
                 [x-amzn-requestid] => fd914721-2a41-49bd-a482-ad0ec8b21e4c
                 [x-amzn-errortype] => AccessDeniedException
                 [x-amz-apigw-id] => TSfV7GtQDoEEh_Q=
                 [x-cache] => Error from cloudfront
                 [via] => 1.1 2080aae7ace369c71819923852e1b17e.cloudfront.net (CloudFront)
                 [x-amz-cf-pop] => YUL62-P2
                 [x-amz-cf-id] => ZH4BqNEJoNKwG5AlBPg0yAd5bxyqf1R0_BjlyjcSEP-HkGB4b3tzLQ==
             )
     )
 [body] => {"Message":"User is not authorized to access this resource with an explicit deny"}

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Antonio Villegas

    (@avillegasn)

    Hi @donbowman,

    What is the value you set in the field ‘WordPress REST API ENDPOINT’ that comes under the selector where you set ‘REST API’?

    I checked the endpoints in the site you mentioned and I didn’t find any additional endpoint name. Note that you need to set up an endpoint name for the proxy to work.

    Thread Starter donbowman

    (@donbowman)

    i did set up the endpoint, and then instrumented the ‘proxy’ function in the php to see it was called (that’s where the output is from).

    I have turned it off for now.

    i used /ab/api i think. i verified the endpoint was shown in the wp-json output alongside the others (in the namespaces object). I verified it called the proxy function, and then sent that request to the upstream, which returned the 403.

    the 403 was returned from api.nelioabtesting.com / cloudfront, as was the reason.

    curl –cookie ver=staging https://www.agilicus.com/wp-json/ | jq | more

    you can see the ‘ab’ namespace on my staging site (which is routed via blue/green testing on this cookie).

    • This reply was modified 1 year, 1 month ago by donbowman.
    Plugin Author Antonio Villegas

    (@avillegasn)

    It seems that you run out of quota. That’s why you received that message from our server.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘cloud proxy 403’ is closed to new replies.