When I pass the url by the Facebook debugger I receive the "Critical error"
"URL requested a HTTP redirect, but it could not be followed."
The redirected URL is the same as the Fetched and Canonical with the added "?AspxAutoDetectCookieSupport=1". So the link rejects this .
I tried the cookieless = UseCookies at Web.config in order to avoid the cookiesupport parameter in the URL but nothing happens , is still there.
this is the section in web.config :
<sessionState cookieless="UseCookies"/>
Is this fine?
Another way for suppressing the parameter?
Its a Facebook cache issue?
You can try it :
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fdisaweb.com%2FModulos%2Ftorre-noria-11.aspx
Thanks in Advance
You're link redirects to:
http://disaweb.com/modulos/torre-noria-11.aspx/?AspxAutoDetectCookieSupport=1
but that returns a 302 to the same location. You can't return a 301 or a 302 to the exact same location that is requested.
Related
I have many redirection with my .htaccess.
Some of my url works fine but others not working.
Many of my url are broken and give this result :
I try this :
Redirect 301 https://mywebsite.com/old-directory/old-directory/old-content https://mywebsite.com/new-directory/new-directory/new-content
And the url give me a 404 error with this url : https://mywebsite.com/new-directory/new-directory/old-content
it's like the redirection is not finished.
I am trying to create a surveymonkey webhook to receive my survey response and i am passing my SugarCRM custom entry point URL as "Subscription Url". But i am getting error " 'mycustomEntryPointUrl' did not return a success status code. Status code is 301". My Entry point is working fine if i run it in browser using its URL also my Sugar is working smoothly.
So, i just want to know any other reason which can cause this error.
Yes so HTTP status code 301 means the page has moved permanently. If you visit it in your browser, for example, you would see a network request to the page specified with a status code of 301, then a second one to the new page. Our API request won't do any redirect, so if a 301 is returned it will raise an error.
This sometimes happens when you go to a page with http and then it redirects to https due to rules on your server.
You also want to make sure your subscription URL supports a HEAD request without any redirect.
I want to publish my first Facebook application and a Privacy Policy URL is required.
I have the page privacypolicy.html published in my website but I get the next message when I configure it in "App Details":
You must submit a valid Privacy Policy URL in order to be compliant with Facebook Platform. Request failed with error:
Bad Response Code: URL returned a bad HTTP response code.
The http code returned when I request the page is 200
Any ideas?
The URL is cached by facebook.
Adding # at the end of my Url did the job ..
This is an old question I know, but I figured I'd post my solution and hope it helps anyone. For me I got this error because I had rewrite rules that didn't catch the URL that Facebook actually goes to in order to get the privacy policy. Facebook adds a query string to the URL that you give it for the privacy policy and since my privacy policy page doesn't do anything with the query string, I didn't check for it in my rewrite rule.
You can check out how Facebook scrapes the page you give it by going to Facebook's Sharing Debugger and putting your URL in the input bar. You can also see the last time that Facebook tried to scrape that URL and tell Facebook to try again once you've fixed any issues. This will get around the caching that was mentioned in user2390340's post.
Facebook externalhit appears to request via the ipv6 address published in DNS if there is one available and won't check on the ipv4 published in DNS.
If your website doesn't have ipv6 enabled it'll return a 404 or 500 and you'll get that error "Bad Response Code: URL returned a bad HTTP response code" for your Privacy Policy URL.
Edit:
Also noted that Facebook caches the URL, I was checking it and getting a "bad response code" error even though there was no hit from their UA in the access logs.
Adding ?stuff onto the end of the URL in the Privacy Policy field bypassed a cache and the access log hits showed up with 200 OK, allowing the URL to be saved.
Not sure if this is related to user2259887's comment about Facebook using IPV6 DNS. But after reading his comment, I was able to work around the validation issue by specifying an IP Address URL instead of using the host domain name URL.
This workaround will not work well if the site IP address is dynamic or change often.
I'm trying to do a simple Redirect 301 but I'm experiencing an issue in this case:
This is my redirect:
Redirect 301 /negocios/wisconsin/wi/ www.domain.com/directorio/category/121/Wisconsin.html
When I enter this URL:
www.domain.com/negocios/wisconsin/wi/servicios-multiples/
It applies the Redirect rule and sends the browser to this URL:
www.domain.com/directorio/category/121/Wisconsin.htmlservicios-multiples/
Which is a WRONG url. Probably because a part of the URL (/negocios/wisconsin/wi/) is similar to the URL I'm trying to redirect.
How I can do to apply the Redirect ONLY to this URL (/negocios/wisconsin/wi/) even if I enter another URL similar like for example
www.domain.com/negocios/wisconsin/wi/WHATEVER-HERE
Try using a RedirectMatch instead:
RedirectMatch 301 ^/negocios/wisconsin/wi/$ www.domain.com/directorio/category/121/Wisconsin.html
This tells apache only to redirect on the exact match instead of linking path nodes together, which is what Redirect does.
I'm trying to pass some variables to my facebook app from the url, i.e. using GET variable app_data like facebook wants.
At some point I've stopped getting the ['signed_request'] part of the $_REQUEST. When I print_r($_REQUEST) I'm getting: ['doc'], ['user'], ['__utmz'], ['__utma'] and ['session'] values, but not signed request :(
Any ideas of why this might be happening?
Check the tab/canvas url is EXACTLY the same as required. If there is a redirect to another page, then signed request and other values will not be sent. You can check using a browser sniffer, if a call to the page responds with a 300 (301/302 etc) redirect, then you need to change to what it redirects to.
Examples:
https://example.com/ may need to be https://www.example.com/ (add www., or remove www. depending on how server is set up)
www.example.com/ may need to be www.example.com/index.php (add index.php, or the right page).
Check you are using http:// and https:// correctly in the URLs, and that https:// returns a valid page.
I've only been able to get the signed request in https://, i get no request at all in http.
Currently have a bug on FB, but no word on fixing it yet; http://developers.facebook.com/bugs/264505123580318?browse=search_4eb3ef23eb18d6649415729
EDIT:
http://SITE.com was redirecting to http://www.SITE.com, so I was loosing the request variables.
Had a similar issue, for me it was as simple as a mismatch of the app id and app secret! However in facebook developers backend I have noticed that the URLs all need to have that trailing slash!
Some browsers do redirect your request to https automatically if you have been on this particular site on https so if you are in http mode on facebook there is situation:
facebook requests http version of your app, browser redirect this request of facebook to https and POST data and thus signer_request are gone in this process...
i see this problem in chrome 23, if you delete browsin data (particulary Deauthorize content licenses) app should run back on http