blocks|key|2922720|text|答案很简单：不可能是。如果主机发生更改，则需要使用绝对路径。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2922721|entityMap^0|6|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Simple answer: not possible.
You need to use an absolute path if the host changes.

blocks|key|2922748|text|这可以通过设置window.location.port属性使用JavaScript来实现。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2922749|<a+href="#"+onclick="javascript:window.location.port=8080">go</a>|code-block|syntax|javascript|2922750|entityMap^0|7|K|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

This can be achieved using JavaScript by setting the <code>window.location.port</code> property.

<pre><code>&lt;a href="#" onclick="javascript:window.location.port=8080"&gt;go&lt;/a&gt;
</code></pre>

blocks|key|249580|text|您不能在相对URL中更改授权的任何部分(即host:port部分)。请参阅RFC+3986的section+5.2.2中描述的算法，了解相对URL是如何解释的。需要注意的重要一点是，权限只是从基本URL或要解析的URL复制而来，而权限的结构永远不会被解释。这意味着您不能更改它的任何部分，包括端口部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|249581|下面是从RFC复制的伪代码中的算法|249582|++--+The+URI+reference+is+parsed+into+the+five+URI+components
++--
++(R.scheme,+R.authority,+R.path,+R.query,+R.fragment)+=+parse(R);

++--+A+non-strict+parser+may+ignore+a+scheme+in+the+reference
++--+if+it+is+identical+to+the+base+URI's+scheme.
++--
++if+((not+strict)+and+(R.scheme+==+Base.scheme))+then
+++++undefine(R.scheme);
++endif;

++if+defined(R.scheme)+then
+++++T.scheme++++=+R.scheme;
+++++T.authority+=+R.authority;
+++++T.path++++++=+remove_dot_segments(R.path);
+++++T.query+++++=+R.query;
++else
+++++if+defined(R.authority)+then
++++++++T.authority+=+R.authority;
++++++++T.path++++++=+remove_dot_segments(R.path);
++++++++T.query+++++=+R.query;
+++++else
++++++++if+(R.path+==+"")+then
+++++++++++T.path+=+Base.path;
+++++++++++if+defined(R.query)+then
++++++++++++++T.query+=+R.query;
+++++++++++else
++++++++++++++T.query+=+Base.query;
+++++++++++endif;
++++++++else
+++++++++++if+(R.path+starts-with+"/")+then
++++++++++++++T.path+=+remove_dot_segments(R.path);
+++++++++++else
++++++++++++++T.path+=+merge(Base.path,+R.path);
++++++++++++++T.path+=+remove_dot_segments(T.path);
+++++++++++endif;
+++++++++++T.query+=+R.query;
++++++++endif;
++++++++T.authority+=+Base.authority;
+++++endif;
+++++T.scheme+=+Base.scheme;
++endif;

++T.fragment+=+R.fragment;|code-block|syntax|javascript|249583|entityMap|0|LINK|mutability|MUTABLE|url|https://www.rfc-editor.org/rfc/rfc3986|1|https://www.rfc-editor.org/rfc/rfc3986#section-5.2.2|2^0|11|8|0|1A|D|1|0|4|3|2|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|F|3|G|5|H|7|16|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]|U|$5|N|O|P|C|$Q|R]]]]

You cannot change any part of the authority (i.e. the host:port part) in relative URLs.
See the algorithm described in <a href="https://www.rfc-editor.org/rfc/rfc3986#section-5.2.2" rel="nofollow noreferrer">section 5.2.2</a> of <a href="https://www.rfc-editor.org/rfc/rfc3986" rel="nofollow noreferrer">RFC 3986</a> to see how relative URLs are interpreted. Important thing to notice is that authority is simply copied from base URL or from the URL being resolved and authority's structure is never interpreted. This implies that you cannot change any of its parts, including the port part.
Here's the algorithm in pseudo-code copied from the <a href="https://www.rfc-editor.org/rfc/rfc3986" rel="nofollow noreferrer">RFC</a>:
<pre><code> -- The URI reference is parsed into the five URI components
 --
 (R.scheme, R.authority, R.path, R.query, R.fragment) = parse(R);

 -- A non-strict parser may ignore a scheme in the reference
 -- if it is identical to the base URI's scheme.
 --
 if ((not strict) and (R.scheme == Base.scheme)) then
 undefine(R.scheme);
 endif;

 if defined(R.scheme) then
 T.scheme = R.scheme;
 T.authority = R.authority;
 T.path = remove_dot_segments(R.path);
 T.query = R.query;
 else
 if defined(R.authority) then
 T.authority = R.authority;
 T.path = remove_dot_segments(R.path);
 T.query = R.query;
 else
 if (R.path == &quot;&quot;) then
 T.path = Base.path;
 if defined(R.query) then
 T.query = R.query;
 else
 T.query = Base.query;
 endif;
 else
 if (R.path starts-with &quot;/&quot;) then
 T.path = remove_dot_segments(R.path);
 else
 T.path = merge(Base.path, R.path);
 T.path = remove_dot_segments(T.path);
 endif;
 T.query = R.query;
 endif;
 T.authority = Base.authority;
 endif;
 T.scheme = Base.scheme;
 endif;

 T.fragment = R.fragment;
</code></pre>

blocks|key|246683|text|您可以简单地在href属性中编写：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|246684|/:port/[path/]file.ext|code-block|syntax|javascript|246685|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Simply you can write in href attribute:

<pre><code>/:port/[path/]file.ext
</code></pre>

We are all familiar with relative paths: A relative path to <code>./images/hello.jpg</code> from <code>http://www.domain.com/hey</code> links to <code>http://www.domain.com/hey/images/hello.jpg</code>.

Problem: How do you state a relative path to <code>http://www.domain.com:1234</code> when you are at <code>http://www.domain.com/hey</code>?

Relative Path, but for Port?

我们都熟悉相对路径:从http://www.domain.com/hey链接到http://www.domain.com/hey/images/hello.jpg到./images/hello.jpg的相对路径。问题：当您在http://www.domain.com/hey时，如何声明http://www.domain...

问相对路径，但是端口？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问相对路径，但是端口？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问相对路径，但是端口？
EN