Results 1 to 5 of 5
  1. pigsflew's Avatar
    Posts
    46 Posts
    Global Posts
    48 Global Posts
       #1  
    Hi everyone, I was told to ask this here:

    I'm getting reports of Curl fetches failing on downloading my two packages in the Precentral feeds:

    begin
    Nothing Interesting.
    failed
    -1: Unable to run command: /usr/bin/curl -s -I --user-agent Preware --location --fail --show-error http://www.precentral.net/downloads/...ouchpad-volume 2>&1

    FWIW, I can get the package from that link using a standard browser or wget, but curl does fail from my ubuntu machine.

    Could it have to do with the precentral->webosnation name change?
  2. #2  
    Seems to be a problem with 301 then (this is from osx):
    EDIT Sorry it's not working, as you said:
    Code:
    /usr/bin/curl -s -I --user-agent Preware --location --fail --show-error http://www.precentral.net/downloads/touchvol
    HTTP/1.1 301 Moved Permanently
    Server: nginx/0.8.54
    Date: Mon, 19 Dec 2011 19:30:27 GMT
    Content-Type: text/html
    Content-Length: 185
    Connection: keep-alive
    Location: http://www.webosnation.com/downloads/touchvol
    
    HTTP/1.1 302 Found
    Server: nginx/0.8.54
    Date: Mon, 19 Dec 2011 19:30:28 GMT
    Content-Type: text/html; charset=utf-8
    Connection: keep-alive
    Status: 302
    X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 2.2.15
    Location: http://cdn.precentral.net/resources/applications/000/016/218/com.wordpress.touchcontrol.touchvol_0.1.0_all.ipk?AWSAccessKeyId=0C0KVER6K3Z6V5NH80R2&Expires=1324330228&Signature=3ewpUUlY3afDFIXEnCbPt4ELSmw%3D
    X-Runtime: 140
    Content-Length: 280
    Set-Cookie: _cms_session=BAh7BzoPc2Vzc2lvbl9pZCIlMDNjMzc4YjExYmQ3ZDI0Yzg2MjkwNmJiNTBiM2IxZDA6E21vYmlsZV9icm93c2VyRg%3D%3D--d10c3e75f3ba435a499f5ff8851b3756cb832ce1; path=/; expires=Mon, 26-Dec-2011 19:30:28 GMT; HttpOnly
    Cache-Control: no-cache
    
    curl: (22) The requested URL returned error: 403
    Last edited by somline; 12/19/2011 at 01:32 PM.
  3. #3  
    Some more info from wikipedia:
    In the HTTP protocol used on the World Wide Web, 403 Forbidden is an HTTP status code returned by a web server when a user requests a web page or media that the server does not allow them to. In other words, the server can be reached, but the server declined to allow access to the page. This response is returned by the Apache web server when directory listings have been disabled. Microsoft IIS responds in the same way when directory listings are denied. (This response may also be returned by the server if the client issued a WebDAV PROPFIND request but did not also issue the required Depth header, or issued a Depth header of infinity.)[1]
  4. pigsflew's Avatar
    Posts
    46 Posts
    Global Posts
    48 Global Posts
       #4  
    Yes, but why does it work from wget or a browser? (Just seems to me it should either fail in both places, or fail in neither).
  5. #5  
    Sorry I'm no expert in this. Take it as a proof, that this happens to me on osx as well.

Posting Permissions