My best guess and according to most references from google searches lead to sessions, cookies or the database data integrity, which eventually could cause this. This redirection issue has only to do with browser requests.
#TUMBLR LOGIN INFINITE REDIRECTS ANDROID#
Other Android Nextcloud clients as well as my Thunderbird mail client connected to the DAV still work and sync data. The files read write permission is verified. I use it for other severs too which work fine. htaccess part as the nginx reverse proxy as well were untouched. But after reverting the config back to original state (without redis) the problem persists. My first suspicion was redis, which has never been used before and which is managing the sessions. The redirect problem is affecting the login part only, as much as I realized. Shows the appropriate page and all the further navigation works as usual. Afterwards the successfull login tries to redirect back to the root path and I guess to the /index.php/apps/files path, but fails with same error. * Connection #0 to host nc.-.eu left intact The main issue is a TOO_MANY_REDIRECTS failure when visiting the root nextcloud address Server tries to redirect to the login page, but after several attempts (see apache log below) it fails with the “Site isn’t redirecting properly” message. These actions can have to do with my issue, thus mentioning them. Verified and caching in redis worked fine I recently checked for issues in the NC admin zone and I did fixing missing indexes on tables and the swtich to utf8mb4 with the occ cli commands.Īfterwards I set up my docker-compose.yml to incorporate redis to manage the memory caching. Var linkSet = document.querySelectorAll('a') Ī system and version: Debian GNU/Linux 10 in Docker imageĪpache or nginx version: Apache/2.4.38 (Debian)
#TUMBLR LOGIN INFINITE REDIRECTS CODE#
If you, like some people, do not like the use of jQuery when a vanilla JS solution is perfectly viable, you could totally use this code instead: Hope this helps you out if you’ve been getting a lot of broken links and please like and/or reblog if this has been useful to you, thank you!! (Note that I’m using the old syntax for initialize.js which has now been depreciated by the authors) Thus I rely on the help of initialize.js plugin to help run the function again every time a new tumblr redirect link is introduced into the DOM. With infinite scroll (or if any links are loaded dynamically into the DOM), the loop will not run on the new links as it’s set to run on document.ready. attr() again to change the href of the original link. Following that I use JavaScript’s decodeURIComponent function to change the remaining string back into a normal URL, since what we get after the previous step has got all those %s and ugly stuff replacing our regular slashes and colons. attr() and remove all the unnecessary parts with JavaScript’s string split() method, picking out the correct part of the arrays that I want. Then I get the entire long redirect URL with jQuery’s. each(), I run a loop through all the links on the blog that have the tumblr redirect syntax (which looks something like t./redirect). remove tumblr redirects script by //using old initialize.js plugin with old syntax As per before, the jQuery library is unnecessary if you’ve already got one in your theme but the initialize.js plugin is important!
If you’ve got infinite scroll installed or some other funky way of loading more links to your blog, you’ll have to use this version instead so that the script will also work on all the new links. Var replaceURL = decodeURIComponent(originalURL) remove tumblr redirects script by originalURL = $(this).attr("href").split("?z=").split("&t=") (The jQuery library is unnecessary if you’ve already got one in your theme) Make the external links on your blog go from this: to this: simply by copying and pasting this following code into your HTML: Basically were pissing me off, so I decided to post this simple script I wrote to fix redirect errors that will hopefully piss them off too :^)
0 kommentar(er)
