Reverse Proxy Cache – L3 / Facebook
-
We are using WSL, and ran into a challenge.
The site is hosted on EC2, Using Reverse Proxy (L3 Memory Cache). We have added the WSL Url to the Whitelist/non cache list. After adding the URL to the Whitelist Google+ works perfect, however Facebook still returns the authentication error (below).
The URL Structure is:
sub.blog.domain.com/blog (primary url)
sub.domain.com/blog (masked url via reverse proxy)We have tried a combinations of the above 2 URL’s in Facebook Dev App and still no luck. in The WSL error log the URLs are showing as the primary url, even though the request is coming from the masked URL. Which I am assuming this is the primary with the mix/match.
Any ideas on how to fix?
If we bypass reverse proxy for the entire site it works perfect.
ξ Authentication failed! Facebook returned an invalid user id. 400. {"error":{"message":"Error validating verification code. Please make sure your redirect_uri is identical to the one you used in the OAuth dialog request","type":"OAuthException","code":100}}
- The topic ‘Reverse Proxy Cache – L3 / Facebook’ is closed to new replies.
