the photo_url given in the eventSearch method appears to be wrong, or unauthenticated. I'm able to get the correct one via eventInfo -- but that seems like a useless extra call to me. What's the story?
I can't seem to reproduce the problem. Can you let me know which event IDs you're seeing the bad photo URL for?
It seems to be any photo_url from event.search when fetched with CURL.
If you're looking at it in a browser -- especially when logged into your Yahoo account -- you won't see the problem. Yesterday I had the same problem even when logged out of my Yahoo account in a web browser. Today it works while logged out in a web browser but not with curl.
I'm afraid I'm still unable to reproduce the original problem -- as far as I can tell, photo URLs return the same status regardless of signed in/out status. Also, as of right now, both event.search and event.getInfo return the same valid photo_url for me, which is accessible in my browser as well as with `curl -sS -L -m 15`:
I'm not sure if this is applicable to your application, but just in case, I will note something about the photo URLs that is not in our documentation yet -- they are temporary. For example, the second URL in your post that was previously working (http://a323.yahoofs.com/upcoming/2886/sm_c5c71722da8916.jpg?upAki1LBbU2vpP7R) is no longer valid. For this reason, if you are caching photo URLs locally in your system, you may want to periodically refresh them or fetch them from our API dynamically.