blocks|key|37188|text|我想出了这个问题的解决方案，但我的方法确实使用了document.referrer.|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|37189|关于使用document.referrer时的UX退化问题，只要您的客户端代码得到优化，它就几乎不会被注意到。|37190|此外，您可能对阅读这篇MDN文章感兴趣。我的解决办法附在这里：|37191|​|37192|const+isExternalURL+=+(url)+=>+new+URL(url).origin+!==+location.origin;

function+checkExternalURL()+{
++const+referrerPage+=+document.referrer;
++if+(referrerPage+==+undefined)+return+false;
++return+isExternalURL(referrerPage);
}

if+(checkExternalURL())+{
++console.log("External+URL+Detected");
}+else+{
++console.log("Internal+URL+Detected");
}|code-block|syntax|javascript|37193|37194|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.mozilla.org/en-US/docs/Web/Performance/How_long_is_too_long^0|O|H|0|0|9|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|13|8|@]|D|@$9|14|A|15|1|16]]|E|$]]|$1|J|3|K|5|6|7|17|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|18|8|@]|D|@]|E|$O|P]]|$1|Q|3|K|5|6|7|19|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]]]

I came up with a solution to the problem, but my approach does use document.referrer.
Regarding UX degradation when using document.referrer, it should be barely noticeable as long as your clientside code is optimized.
Also, you might be interested to read <a href="https://developer.mozilla.org/en-US/docs/Web/Performance/How_long_is_too_long" rel="nofollow noreferrer">this MDN Article</a>.
My solution approach is attached here:
<div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-js lang-js prettyprint-override"><code>const isExternalURL = (url) =&gt; new URL(url).origin !== location.origin;

function checkExternalURL() {
 const referrerPage = document.referrer;
 if (referrerPage == undefined) return false;
 return isExternalURL(referrerPage);
}

if (checkExternalURL()) {
 console.log("External URL Detected");
} else {
 console.log("Internal URL Detected");
}</code></pre>
</div>
</div>

blocks|key|36353|text|window.location.replace有完全相同的要求，请参考https://developer.mozilla.org/en-US/docs/Web/API/Location/replace|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|36354|假设外部重选页面只包含用于重定向的逻辑，而不包含任何内容，则应该使用location.replace进行重定向，以获得干净的历史状态。|36355|我知道您对外部站点没有控制权，但我只是想提供帮助，以防您可以要求某人在那里进行更改:)|36356|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.mozilla.org/en-US/docs/Web/API/Location/replace^0|Z|1T|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

window.location.replace is there for exactly the same requirement, please refer <a href="https://developer.mozilla.org/en-US/docs/Web/API/Location/replace" rel="nofollow noreferrer">https://developer.mozilla.org/en-US/docs/Web/API/Location/replace</a>
Assuming that the external rediection page contains only the logic for rediection and no content, they should have used location.replace for redirection to have a clean state of history.
I know that you do not have control over external site but I just wanted to help in case you can ask someone to make changes there :)

Let's say an external site has a redirection page before actually moving to the internal site when user clicks the link.
This internal site only has a button that will let you go back using
<a href="https://developer.mozilla.org/en-US/docs/Web/API/History/back" rel="nofollow noreferrer">History.back()</a> or .go(-x). I can only do changes on the internal site.
What's happening here is that we now have a &quot;loop&quot; that redirects to the external redirection page using history.back(), and then the user will be redirected once again to the internal site.
Flow:
External site -&gt; user clicks on internal site link -&gt; external site sends user to external redirection page -&gt; user redirects to visit the internal site -&gt; user click history.back button -&gt; user get redirected to external redirection page -&gt; user redirects to visit the internal site again
I basically do not want the user to end up at the internal site after users clicks the history.back button.
I thought about saving page visit in localstorage, so that if it gets redirected back to the internal site again it will instead do history.go(-2).
I am also aware of <a href="https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer" rel="nofollow noreferrer">https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer</a> document.referrer, but that will also degrade the UX since the user gets redirected back and forth at least once.
The only solution I could think of is having a query parameter upon visiting the internal site someurl.com/?redirects=2, so that we could do history.go(-redirects). However, that requires the external site to decide how many redirects it has.
Is it possible to know if user comes from a redirection page from the external site? Is there a way so that we can skip the external redirection page and just go straight to the external page?

How to skip external redirection page using history back function?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

假设外部站点在用户单击链接时实际移动到内部站点之前有一个重定向页面。这个内部站点只有一个按钮，可以让您使用或.go(-x)返回。我只能在内部网站上做更改。这里发生的情况是，我们现在有一个使用history.back()重定向到外部重定向页面的“循环”，然后用户将再次被重定向到内部站点。流动：外部站点->用户单击内部站点...

问如何使用历史回送函数跳过外部重定向页？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用历史回送函数跳过外部重定向页？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用历史回送函数跳过外部重定向页？
EN