| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 65
|
|
| Author |
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1684 Status: Offline Project Badges:
|
Since 2016-12-21, at about 22:00 UTC, I receive an "error 301" by fetching the .json files containing the current WU status.
----------------------------------------Since end of November 2016, I have a bash script using curl collecting the .json files. It ran fine until 2016-12-21, 22:00 UTC, since this time the json files are empty or report "error 301". Surprinsigly, 2016-12-21, 22:00 UTC, the same curl invocation in CLI or https invocation in a web browser deliver the expected result. Since the script has not been modified and two hosts are impacted in a similar way, I am a little desperate. In advance, I thank you for any help. Cheers, Yves --- FYI: Last successful collection: 2016-12-21T21:44:00 UTC, first failed collect 2016-12-21T22:21:00 UTC |
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1684 Status: Offline Project Badges:
|
I've just found the cause for this Error 301: the api invocation changed.
----------------------------------------
At the TechTeam, did I miss an announcement ? ... Yves |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Either path works here when calling, but https://secure. redirects to https://www., noting that I resented to have to set redirect permission in the IE object.
|
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
KerSamson,
You are correct that we failed to provide information about a release yesterday. We have been doing a series of small updates to the website over the past couple of months to remove the use of EJB 2.1 from our website code (much of this code dates back to 2004/2005). Not much has changed from a end user perspective with these releases and so we have not been saying much about them. Yesterday we did another release. It was exciting for us in that it removed the last of the EJB 2.1 code from our system. However, nothing really changed from a end user perspective. However, we are in the process of moving the site to running only under https. Right now, all secure actions that you take on the website are done under https and in fact you can have your entire experience under https. However, we did not force the browser to always use https. After this change is complete, your entire website experience will be under https. Most of this change was released yesterday. We ran into one issue with the load balancer so we will not be able to complete that change until we make a change to the load balancer. As part of the change we will now have https://www.worldcommunitygrid.org be the canonical domain for our website. We originally differentiated between 'www' and 'secure' for the http vs https back when we launched in 2004 in order to highlight what was encrypted and what wasn't. The thinking around https was quite different back then (the recommendation was to use it as little as possible because of the higher load on the webservers). This thinking is completely different now and thus we are moving to just www.worldcommunitygrid.org. Additionally, the mix of www.worldcommunitygrid.org and secure.worldcommunitygrid.org has an impact on search rankings, messes with stats on social sharing and other SEO type items, so making a single subdomain for all of our traffic we will give a bit of a benefit there as well. I apologize for the issue this caused you and our lack of announcement. I'm glad you were able to find the issue and resolve it. Please let us know if you find any additional items that this change is causing issues for. thanks, Kevin |
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1684 Status: Offline Project Badges:
|
Hi Kevin,
----------------------------------------I thank you warmly for your exhaustive explanation. Being honest, I did not identify immediately this small difference, even if it was correctly reported with the Error 301. Since I have four students working on a WCG reporting tool project, I was really concerned, hoping that they will not be disturbed with this issue. It was the reason why I've tried to investigate so fast as possible. Nevertheless, as usual, the solution was clearly mentioned but I missed it at first (01:00 CET in the morning). Since you are working on improvement, I would really appreciate that we will have the possibility to collect the "Statistics By Project" (see the project list on MyContribution page: Statistics By Project) as .json or .xml with the same mechanism (API) as for the WU results. If it is unfortunately not possible, at least the .html source should tag the "Statistics by Project" list (table) with a dedicated <div> attribute for simplifying the grabbing work. It would be a great Christmas gift for long time contributors Such gift is also accepted after Christmas I take this opportunity to wish you, your Family, and your colleagues a great Christmas time. Cheers, Yves ---------------------------------------- [Edit 1 times, last edit by KerSamson at Dec 22, 2016 2:44:36 PM] |
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1684 Status: Offline Project Badges:
|
@ SekeRob
----------------------------------------The redirection works fine in the web browser but not in a curl invocation. In such case, I received a small file containing the Error 301 or an empty file. It is the reason why I struggled a little bit for finding the cause and the solution. Cheers, Yves |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7849 Status: Offline Project Badges:
|
Kevin, thanks for the explanation.
----------------------------------------I do have one additional issue. I have been using the following query to get results:"(https:)//secure.worldcommunitygrid.org/api/members/sgt.joe/results?code=********************************&xml=true&limit=250&ServerState=5&ValidateState=1". I know about the change eliminating the "secure" from the query, but that still gave me an error. It turns out that a space is needed between the last "&" and the "ValidateState=1" whereas this was not previously necessary. With the space inserted, it once again works perfectly. Cheers Edit: I put the parentheses around the https so the entire query would show as a text string rather than a link.
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 4 times, last edit by Sgt.Joe at Dec 24, 2016 6:38:51 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Start reading here: https://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=536562 , presuming the extra space was the 'small issue'.
|
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7849 Status: Offline Project Badges:
|
Start reading here: https://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=536562 , presuming the extra space was the 'small issue'. Yes, I had read that, and double checked I was using the correct case sensitive version. Just thought I would mention what was the "fix" for (in my opinion) the newly introduced bug. I always appreciate your input on these issues as you seem to be way ahead of the rest of the pack. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
ErikaT
Former World Community Grid Admin USA Joined: Apr 27, 2009 Post Count: 912 Status: Offline Project Badges:
|
Since you are working on improvement, I would really appreciate that we will have the possibility to collect the "Statistics By Project" (see the project list on MyContribution page: Statistics By Project) as .json or .xml with the same mechanism (API) as for the WU results. Hello KerSamson,This is not something that we can do immediately; therefore, I have added it to the backlog. Thank you for your support, ErikaT |
||
|
|
|