-
Notifications
You must be signed in to change notification settings - Fork 9
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
serviceWsdl attribute value not using actual domain name #191
Comments
I've changed the config to use the actual service wsdl that works. Thanks. |
Cool, thanks! I didn't realize this was hardwired in the config file. Are you saying you updated the config file(s) that's deployed on our AWS, or the ones on the wofpy repo? Is your change a generic one that will ensure this problem doesn't come up again for anyone -- namely, the appropriate domain is used for test vs production environments? FYI, this isn't a high-priority issue. |
AWS.
This change should be noted in the the documentation, because it is hardwired in config file. I can try to figure out a way to automate it, if that's better in the long run. |
Thanks for the clarification.
Exactly. Again, low priority, but if you think it's easy, go right ahead. |
In
GetSiteInfo
responses, theseriesCatalog
element includes an attribute calledserviceWsdl
. Currently the value of the attribute uses the localhost domain:port, http://127.0.0.1:8080, rather than the actual domain name (and port) for the wofpy instance. I'm not certain (we'd need to look at WOF/WaterML specs and non-wofpy live WOF instances), but it'd make more sense if this url was the actual WSDL url, not a useless url.Example from our live demo:
Request: http://54.186.36.247:8080/mysqlodm2timeseries/rest/1_1/GetSiteInfo?site=mysqlodm2timeseries:USU-LBR-Mendon
Code chunk:
The text was updated successfully, but these errors were encountered: