Join the Facebook Fan Page.
Started by Sebastiii, December 06, 2020, 02:27:22 PM
Quote// If we're viewing a topic, these should be the previous and next topics, respectively. if (!empty($context['current_topic'])) echo ' <link rel="prev" href="', $scripturl, '?topic=', $context['current_topic'], '.0;prev_next=prev" /> <link rel="next" href="', $scripturl, '?topic=', $context['current_topic'], '.0;prev_next=next" />';
127.0.0.1 - - [11/Dec/2020:13:50:26 -0800] "GET /yadayada/index.php?topic=2.0 HTTP/1.1" 200 5650...127.0.0.1 - - [11/Dec/2020:13:50:29 -0800] "GET /yadayada/index.php?topic=2.0;prev_next=next HTTP/1.1" 200 5442
Quote from: vbgamer45 on December 11, 2020, 06:35:43 PMVery interesting thanks for looking into it! Should help with sever load but generally i don't think many people use those links in topics.
Quote from: shawnb61 on December 11, 2020, 06:20:37 PMYes, the above works. I have been testing that myself.
QuoteI believe this is a bug in Chrome. In the past, the links above helped search engines deal properly with pagination, but they haven't been used for a while, so they are unnecessary. They are not used in 2.1, which doesn't have this issue.
QuoteAnd their presence definitely causes issues with the latest Chromium-based browsers. The browser generates a "silent" next page request, that is not displayed. But SMF sees the next page request & delivers it & thus marks the page as read.
Quote from: shawnb61 on December 14, 2020, 09:13:01 PMI am fairly sure this is a bug with Chromium itself, that exhibits in both Edge & Chrome.
QuoteWe'll see what comes back from the Chromium team. (They have created accounts on this site & are attempting to recreate on their end... You can see the back & forth here: https://bugs.chromium.org/p/chromium/issues/detail?id=1158209)