Adding a link to a Flickr image gives me an 'undefined' link on the content profile

[bertpareyn]

The Flickr link used: http://www.flickr.com/photos/bertpareyn/9009115086/
Another Flickr link that did work: http://www.flickr.com/photos/iandolphin/9551168427/

[nicolaasmatthijs]

Assigning to @BP323 for investigation

[simong]

FWIW: The PP sets the previews.status to ignored. Maybe the preview widget is ignoring the ignore status?

[bertpareyn]

The Hilary logs produce this for the link:

[2013-08-21T07:12:59.036Z] ERROR: oae-preview-processor/4023 on ds159.lib.private.cam.ac.uk: Could not check whether this URL allows for iframe embedding. (contentId=c:cam:xJGtEmkROg)
    Error: Parse Error
        at Socket.socketOnData (http.js:1553:20)
        at TCP.onread (net.js:525:27)

[bertpareyn]

@simong The PP locally returns status error

[simong]

You probably haven't filled in the flickr API keys so it falls back to the default link processor.
That does a HEAD request to check for iframe embedding but I don't see why that would fail.

I'll dig into it a bit

[simong]

I suspect this is because we're doing a HEAD request that gets redirected (twice) and ends up at an https endpoint. The actual error is { [Error: Parse Error] bytesParsed: 829, code: 'HPE_INVALID_CONSTANT' }

[nicolaasmatthijs]

If this is the only URL that this is really happening for, we probably don't need to fix the preview processor issue as we expect people to configure the Flickr API key. However, the UI should be able to deal with the error status code rather than showing the undefined message.

[simong]

I've created an issue in the backend (oaeproject/Hilary#645) to track the backend part of this issue.

I'll assign this (UI) ticket to @BP323 for dealing with preview errors.

[bertpareyn]

I created a ticket for this in the plugin's Github repo starfishmod/jquery-oembed-all#93

[nicolaasmatthijs]

Closing this in favour of the Github repo ticket. I've also signed up for thread updates.