Skip to main content
P
phil_ashby
Inspiring
September 29, 2010
Question

CFFEED Issue

  • September 29, 2010
  • 1 reply
  • 936 views

Hi all,

I'm trying to use cffeed on our Intranet site so users can pull in external RSS feeds to customise their homepage.

using the basic code of <cffeed source = "#theURL#" properties = "myProps" query = "myQuery"> I get the following error message

"Connection refused by the specified host on the specified port".  Our server support guys say that server is set up correctly (hmmmm) but as the same code works perfectly on an external web server we also have I sorta doubt them!  Does anyone have any idea what the issue might be (apart from the obvious "read the error message!") and how I can get round it?

Thanks

Phil

    This topic has been closed for replies.

    1 reply

    A
    Adam Cameron.
    Inspiring
    September 29, 2010

    Change the template to output #theURL# instead of doing the <cffeed>.  Does the URL as output look valid?

    FROM THE CF SERVER (not your workstation, but actually sitting @ the CF server keyboard (or remote onto it, obviously, but I mean do this next operation on the CF server itself), open a browser and browse to the URL, exactly as it appears on the screen.  Does it work?

    --

    Adam

    P
    phil_ashbyAuthor
    Inspiring
    September 29, 2010

    Hi Adam,

    yes, the URL is coming through fine and when I log onto the server via MSTSC and put the URL in the browser it accesses it fine.  However, I login onto the server using my account details and therefore I think it's using my authentication to access the external site through our firewall. Our server guys reckon that the server is set up correctly, but as I said, if I upload the same code to an external server it works fine...

    Phil

    A
    Adam Cameron.
    Inspiring
    September 29, 2010

    Login as the same user as the CF service uses and try again.

    Or go to your IT guys and show them the test you just performed and get them to revisit their idea of what constitutes "set up properly", because part of being "set up properly" is that it should fulfil the client's - in this case you - requirements.  If it's not doing that, it's not set up properly ;-)

    Can you <cfhttp> that URL?  I would expect you'd get the same error, but worth checking.

    --
    Adam

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices