The 4.x version (so supposed to use push and auto-detect HTTPS) sent us report with GET over plain HTTP even if it detected working SSL:
"Top 404 page: http://[foo.com]/droptorfeed/[hash] (4 times)"
Is this expected that it doesn't use secure connection here even if detected it and that it still needs to GET /droptorfeed/[hash] even if it works in a push mode?
Sorry if that is a silly question, but I would need to read the code to determine this, probably.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | droptor-test-om8.jpg | 276.45 KB | omega8cc |
Comments
Comment #1
jemond commentedSince 4.x uses push, there is no longer any inbound menu route in Drupal. So that will also do a 404. Instead, a Drupal site running 4.x will push the data to droptor, over SSL by connecting to http://www.droptor.com/inbound...
Comment #2
omega8cc commentedThen it is probably a bug, because it is 4.0 what does attempt these requests and reports them as 404.
Comment #3
jemond commentedAh, these are coming in from droptor.com as droptor.com probably doesn't know yet that the site is running 4.x, not 3.x. Has the site synced successfully yet?
Comment #4
omega8cc commentedSo if the site has 4.0 module installed, which is expected to *push* what Droptor needs, Droptor will use *pull* anyway, until it will discover that it is a 4.0 integration module? Shouldn't it simply wait for the push attempt from the site with correct API key entered? I guess it would be hard to achieve for backward compatibility, so it is some initial issue the user could live with.
However, after the site was checked/synced w/o issues, and even if the cron runs on the site every 3 hours, now Droptor reports that the last sync was 3 days ago, so it is out of sync -- see the screenshot:
Not sure then if this really works in the *push* mode, after Droptor already knows it is 4.0 installed, if I would need to manually click on the "Push sync" to get it synced. It is rather confusing if the link in the Droptor control panel says "Push sync" if in fact it is either expected to *pull* for 3.x and *push* for 4.x -- but push from the site, not from the Droptor side.
Comment #5
omega8cc commentedOuch, sorry, the second issue is our system fault -- it disables the Update module daily, so it auto-disables also depending on it Droptor. I will enable it again and run cron to make sure it works.
Comment #6
omega8cc commentedYep, that was it, sorry for the noise.
As for the original issue, I guess it is unavoidable without breaking backward compatibility with 3.x so it should be OK to close this ticket with "works as designed".
Comment #7
jemond commentedThanks for the clarification. Yes, backwards compatible is tricky, and for now at least, Update is a dependency.