-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading of IMF remote conversion data fails. #164
Comments
I experienced IMF API rejections during testing that turned out to be some form of throttling. After 10mins or so my requests got answered again. Maybe its the same case... |
Possible. GitHub API right here causes "abuse rejection" of updating GH-Pages on a regular basis if you try to run it from a Maven job. |
This looks more like User-Agent-based blocking, we started observing the same behaviour. I tried a bit:
So it looks like they at least block Wget and probably javamoney's User-Agent as well |
We also saw similar behavior of many popular Social Media APIs (especially Facebook) or Fitness/QS APIs like Fitbit or Strava. Interestingly that often differs from the context of the call, e.g. calling Strava from a standalone Java app via https://github.com/keilw/JStrava worked well, but doing the same from inside a Java EE container and Agorava caused a bot or DDS-blocking to kick-in. |
Sounds reasonable, maybe we should set the corresponding agent-headers and
see if things change ;)
2017-07-14 13:21 GMT+02:00 Dennis Bliefernicht <notifications@github.com>:
… This looks more like User-Agent-based blocking, we started observing the
same behaviour. I tried a bit:
- moneta (fails)
- Chrome (succeeds)
- wget (fails)
- curl (succeeds)
- curl with User-agent containing the word "Wget" (fails)
So it looks like they at least block Wget and probably javamoney's
User-Agent as well
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC5scxfxzYaRw5ID01rhF-Gz0mz407Cdks5sN08jgaJpZM4OUir4>
.
--
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter: @atsticks, @tamayaconf*
[image: GeeCON] [image: JSD_Speaker_2017]
|
Seems I also ran into something like it when executing TestNG tests from the Maven build job:
|
Added configurable User-Agent header, using chrome as default. Works perfectly. |
Loading of IMF conversion data actually fails (class
org.javamoney.moneta.internal.loader.LoadableResource
): with a default html response of "Request rejected". Interestingly calling the same URL from a browser, e.g. chrome works:http://www.imf.org/external/np/fin/data/rms_five.aspx?tsvflag=Y
As a result the IMF and IMF-HIST rate provider fails to load because the response is a valid input stream, which unfortunately is not parsable to any conversion rates.
I did not check, if the behaviour in the backport is similar.
The text was updated successfully, but these errors were encountered: