Results 1 to 3 of 3
  1. #1
    Join Date
    Jun 2010
    Posts
    13

    Default Error - Didn't receive 200 OK from remote server. (HTTP/1.1 301 Moved Permanently)

    Hi Guys

    Im getting the following error :

    Didn't receive 200 OK from remote server. (HTTP/1.1 301 Moved Permanently)

    This is on a website which needs to automatically post entries onto my Wordpress blog using XMLRPC.

    Theres a setting in Wordpress to enable the remote publishing protocols which i've done.

    The website/domain it is posting to is an addon domain from my master account.

    Could this be the issue and how do i rectify it, im assumeing somethings got to change within the .htaccess file?

    thanks

  2. #2
    Join Date
    Oct 2006
    Location
    localhost
    Posts
    3,375

    Post

    Quote Originally Posted by hostguru View Post
    Hi Guys

    Im getting the following error :

    Didn't receive 200 OK from remote server. (HTTP/1.1 301 Moved Permanently)

    This is on a website which needs to automatically post entries onto my Wordpress blog using XMLRPC.

    Theres a setting in Wordpress to enable the remote publishing protocols which i've done.

    The website/domain it is posting to is an addon domain from my master account.

    Could this be the issue and how do i rectify it, im assumeing somethings got to change within the .htaccess file?

    thanks
    Hi Jay,

    If the site is hosted with us, can you post some more info about your account? Or get in touch with our support technicians to get this sorted quickly? My best guess here is that our Linux server's security is configured to prevent such external postings..

    Rock _a.k.a._ Jack
    Windows Hosting || Windows Reseller Hosting
    Cloud Hosting 100% UPTIME! || Powerful Dedicated Servers
    Follow eUKhost on Twitter || Join eUKhost Community on Facebook

    For complaints, grievances or suggestions kindly email our FeedBack Dept.
    Proper action will be taken accordingly & instantaneously!

  3. #3

    Default

    Well, as I understand, this problem is caused when a server sends the header like:

    Location: /somethingElse.com

    eg. if you try to fetch google.com using php using fsockopen, it will show nearly the same page as you are seeing now.

    The remedy is to get the new location of the page.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •