I get a 404 error while checking the link using requests for the page below while the page opens fine in the browser. Can someone please help me understand what's happening?. I get the same error using this service as well.
url = "http://www.dell.com/en-us/learn/assets/corporate~case-studies~en/documents~2014-chitale-dairy-10012962-networking-blades-support.pdf
response = requests.get(url)
print response.status_code
Seems that Hypertext Transfer Protocol is working fine! The pdf file that you trying access is no longer exist or never existed.
Related
I am getting an error while uploading an image to Facebook.
Both image and image path are proper but somehow it is not uploaded to Facebook when I am making a POST request to {pageid}/photos API call.
Here is my code.
$photoURL = 'https://www.example.com/images/img.png';
$uploadPhoto = $fb->post('/'.$pageId.'/photos', ['published' => 'false', 'url' => $photoURL]);
And it is giving following error.
Message: (#324) Missing or invalid image file
Please help me.
Thanks.
If you are trying to post from your localhost or virtualhost then error occurs because facebook can not find the url that you are providing.
Try this way:
search image from internet and pass its address to facebook SDK. I will post successfullty.
I was trying to send image from my virtualhost http:app.local.com/image-address and it gave same error. Then I picked an image form internet and passed then it was posted successfully.
Hope it solves your issue
For me it was the SSl certificate. It was on the server and valid over https, however I had an incorrect intermediate certificate on there. I saw the error when I checked the domain
https://cryptoreport.geotrust.com/checker/views/certCheck.jsp
Thanks
Grant
I get a 404 error while checking the link using requests library for the page below while the page opens fine in the browser when I reach to it from it's parent page. Can someone please help me understand what's happening?. I get the same error using this service as well.
url = "http://www.dell.com/en-us/learn/assets/shared-content~data-sheets~en/documents~2016-v5-systems-oem-10022706.pdf"
response = requests.get(url)
print response.status_code
The first URL sets a cookie, that is sent to the server as you request the second link. If you call the second link with exactly the same request, excluding the cookie, you get a 404.
We used wso2esb 4..8.1.
We are facing issue when moved into the production some of the requests from client is getting 404 page not found error .Where as everything is working in dev environment
We are facing same issue like above description the difference is we are using F5 Hard ware load balance.
we are able to see request and response printed in wso2carbon.log but client is not getting response and resulting 404 error code.
Please be informed that this problem is happening only for certain requests only not for all.
We tried to reproduce this scenario using Jmeter and Soap UI but did not face this problem. Our doubt is response being dropped going through HLB.
Please suggest.
I am trying a GET request from Facebook for a batch of ids using my app access token separated by a comma.
Please find below the call:
https://graph.facebook.com/?ids=1374186930,100005305471358,1516423103,100003031846875,100002939786624,100004705179654,522691095,100002893804783,100005269178084,1417831236,100004652521769,100003511989378,100002394692546,1646211152,1092931510,100000152985362,100004151552444,100004122698187,100001574061632,100005007584068&access_token=<my_app_access_token>&format=json
Facebook returns an error intermittently for some of these requests with an HTTP status code of 502.
I've tried fetching for these ids using the graph API explorer as well as the app access token later. They have been fetched properly. I have performed some research, but all issues of Facebook were related to open graph and 502 is "Bad Gateway Error". Since mine is not a web app, I cannot even refresh a browser to make the call again. This is a normal call made to Facebook API.
The error returned by Facebook is html which contains the following message:
"Sorry, something went wrong. We're working on getting this fixed as soon as we can."
Since they have given this response, I want to know if someone is facing this issue as well and if somebody could tell me, when this will be resolved.
This is affecting the other calls as well and there is a delay in the fetching.
Thanks in advance.
The Error 502 means that the message is too large. I do not know exactly the maximum size. Curiosity. What language are you using??
Good Bye
I am sending get httpwebrequests to the facebook graph api and all was working fine till I deployed to production server and now module that expects html/xml response is not working and when tested url in internet explorer, the save file dialog pops up and the file needs to be saved.
Other modules also send requests to the facebook graph but just differ in the form of requests so not sure what is going on here.
Any ideas appreciated
Edit:
Let me try and rephrase this. On my production server the httpwebrequest was not returning the correct result. So to Test it I copied the url http://graph.facebook.com/pepsi which is an example, should return the profile info viewable in the browser. The server has internet explorer v8 and I am not sure why it tries to download the file instead of displaying it in the browser. this is what is happening in my code and when I make a request to a different part of the api, then it works in my app but not in the browser
Your question is not very clear. From what I gather, you want the display the JSON response in a browser. Instead, you are being asked to download a file by the browser.
Well, this is normal behaviour. The response you get from Facebook would most likely have a MIME type of application/json. Most newer web browsers display the text in the browser itself. Some browsers, however don't know how to handle this content type and just ask you to download the file.
You mentioned that your module expects an html/xml response. Try changing this to application/json.
You also said that it works in your app but not in your browser. I don't know what you're making, but generally you wouldn't show raw json to the user in a browser, right?