-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
getSymbols.oanda HTTP error 404 #225
Comments
Thanks for the report. I can replicate. Google no longer provides price data. I checked Yahoo Finance and they specify the EUR/USD pair as EURUSD=X, so |
Thanks for the reply. Yes,now I can get from Yahoo. But,what about oanda? I still can't use getSymbols with oanda. Is it maybe because oanda v1 REST API will cease to function? |
The previous URL was returning HTTP 404 errors. Fixes #225.
@MihalisPapatsimpas I just pushed a branch that works for me. Please test to see if it works for you too! |
Thank you @joshuaulrich for your help! To test it,I installed the quantmod package from your repository using the following: devtools::install_github("joshuaulrich/quantmod"). The error still appears. Is this the right way to test it? Thanks again! |
No, that will just pull the current HEAD of master. My patch is on the branch 225_getsymbols_oanda. I think you can pull and install that via: |
I installed the patch in 2 ways. The one you suggested and: |
Is it exactly the same error? I just tried on a different machine and got "HTTP error 400". 400 is "bad request", and 404 is "not found". |
No,sorry i didn't mention it. It is "Error in open.connection(con, "rb") : HTTP error 400" . |
The previous URL was returning HTTP 404 errors. Fixes #225.
I just pushed an update that corrects a mistake I made. It works for me now, I promise. :) |
Yes, now it works perfect!! Thanks for your time! |
I try to get some symbols from Oanda and I can't. I have tried also Google and Yahoo and the result is the same. I try to execute the following and what I get is an error.
The text was updated successfully, but these errors were encountered: