HTTPS issue - Error Code 0403

Topics: Developer Forum, Project Management Forum, User Forum
Jun 30, 2014 at 11:37 AM
Hi there,
after flickr have been switched this weekend fully on https API, an sad error appeared in my experimental app I have writen using your .FlickrNet API library - latest version (3.10.0).
After calling
flickr.StatsGetPopularPhotos(date, (PopularitySort.Views), page, 100)
an web exception - The remote server returned an error: (403) Forbidden - appears.
The same issue with calling flickr.PhotosSearch(searchOptions).

flickr = FlickrHelper.GetAuthInstance() - works OK, however.

My experimental app is coded in C# using .NET framework and it has been working without problems for a year until this weekend. I use it for extensive flickr stats data gathering (download) from my flickr Pro account to be used localy with my local SQLite database processing.

Please, can you help me soon. The retension time period for extensive flickr data stats is 4 weeks, after this period all data are lost.

Thank you in advance.

Jun 30, 2014 at 3:41 PM
Edited Jun 30, 2014 at 3:42 PM

My app is getting the same error as yours. I think we have to change the library, and when it appears "http:/" it has to be "https:/"


Álvaro Real
Jun 30, 2014 at 7:11 PM
after some debuging and trials I have an hypothesis, that
calling url = flickr.OAuthCalculateAuthorizationUrl(requestToken.Token, AuthLevel.Read)
still returns url with http, and NOT https.
Is this that??


Jun 30, 2014 at 7:41 PM
I looks like

return new Flickr(ApiKey , SharedSecret, "1" )

return flickr with http Uri. as here
Jun 30, 2014 at 8:58 PM

The latest version is actually 3.12. You can download it via NuGet. I'll try and upload it to the Release directory at some point in the next few days.

Version 3.10 however should still be returning HTTPS for almost all endpoints (I did miss one in OAuthGetRequestToken() however).

Jul 1, 2014 at 10:06 PM
Great! Thank You, Sam!
It works! After download last version as of 1.July, rebuild and run, everything works perfectly again.
I am very happy, thanks once more.