blocks|key|3072004|text|如果您只关心尾部斜杠的多义性，您可以通过知道NSURL路径修剪尾部斜杠来快速省略这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3072005|但我喜欢在NSURL上使用类别方法的想法，它实现了一些基于标准的等价(在这种情况下，“等价”可能是一个比相等更好的术语)。|3072006|@RobNapier指的是一个相关的问题，它有一个好的答案，指向RFC2616。url语法的另一个相关标准是RFC1808。|offset|length|3072007|困难的部分是决定我们所说的等价性是什么意思，例如，不同的查询或片段(锚链)怎么办？下面的代码对于这些歧义中的大多数都是错误的。|3072008|//+in+NSURL%2BuriEquivalence.m

-+(BOOL)isEquivalent:(NSURL+*)aURL+{

++++if+([self+isEqual:aURL])+return+YES;
++++if+([[self+scheme]+caseInsensitiveCompare:[aURL+scheme]]+!=+NSOrderedSame)+return+NO;
++++if+([[self+host]+caseInsensitiveCompare:[aURL+host]]+!=+NSOrderedSame)+return+NO;

++++//+NSURL+path+is+smart+about+trimming+trailing+slashes
++++//+note+case-sensitivty+here
++++if+([[self+path]+compare:[aURL+path]]+!=+NSOrderedSame)+return+NO;

++++//+at+this+point,+we've+established+that+the+urls+are+equivalent+according+to+the+rfc
++++//+insofar+as+scheme,+host,+and+paths+match

++++//+according+to+rfc2616,+port's+can+weakly+match+if+one+is+missing+and+the
++++//+other+is+default+for+the+scheme,+but+for+now,+let's+insist+on+an+explicit+match
++++if+([self+port]+%7C%7C+[aURL+port])+{
++++++++if+(![[self+port]+isEqual:[aURL+port]])+return+NO;
++++++++if+(![[self+query]+isEqual:[aURL+query]])+return+NO;
++++}

++++//+for+things+like+user/pw,+fragment,+etc.,+seems+sensible+to+be
++++//+permissive+about+these.
++++return+YES;
}|code-block|syntax|javascript|3072009|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ietf.org/rfc/rfc2616.txt|1|http://www.w3.org/Addressing/rfc1808.txt^0|0|0|W|7|0|1I|7|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@$F|11|G|12|1|13]|$F|14|G|15|1|16]]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|18|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]|W|$5|R|S|T|A|$U|X]]]]

If you care only about the trailing slash ambiguity, you can dispense with this question quickly by knowing that NSURL path trims the trailing slash.

But I like the idea of a category method on NSURL that implements some standards-based equivalence ("equivalence" is probably a better term than equality in this case).

@RobNapier refers to a related question with a good answer that points to <a href="http://www.ietf.org/rfc/rfc2616.txt" rel="noreferrer">RFC2616</a>. Another relevant standard for url syntax is <a href="http://www.w3.org/Addressing/rfc1808.txt" rel="noreferrer">RFC1808</a>.

The tough part is deciding what we mean by equivalence, for example, what about differing queries or fragments (anchor links)? The code below errs on the side of permissiveness for most of these ambiguities...

<pre><code>// in NSURL+uriEquivalence.m

- (BOOL)isEquivalent:(NSURL *)aURL {

 if ([self isEqual:aURL]) return YES;
 if ([[self scheme] caseInsensitiveCompare:[aURL scheme]] != NSOrderedSame) return NO;
 if ([[self host] caseInsensitiveCompare:[aURL host]] != NSOrderedSame) return NO;

 // NSURL path is smart about trimming trailing slashes
 // note case-sensitivty here
 if ([[self path] compare:[aURL path]] != NSOrderedSame) return NO;

 // at this point, we've established that the urls are equivalent according to the rfc
 // insofar as scheme, host, and paths match

 // according to rfc2616, port's can weakly match if one is missing and the
 // other is default for the scheme, but for now, let's insist on an explicit match
 if ([self port] || [aURL port]) {
 if (![[self port] isEqual:[aURL port]]) return NO;
 if (![[self query] isEqual:[aURL query]]) return NO;
 }

 // for things like user/pw, fragment, etc., seems sensible to be
 // permissive about these.
 return YES;
}
</code></pre>

blocks|key|3072027|text|简单的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3072028|NSString*urlString=[NSString+stringWithFormat:@"%25@",request.URL];|code-block|syntax|javascript|3072029|因此，将其与NSString方法isEqual进行比较：|3072030|BOOL+equalty=[urlString+isEqual:anotherNSString];|3072031|XD|3072032|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Easy way is:

<pre><code>NSString*urlString=[NSString stringWithFormat:@"%@",request.URL];
</code></pre>

so you compare with NSString method isEqual:

<pre><code>BOOL equalty=[urlString isEqual:anotherNSString];
</code></pre>

XD

blocks|key|214860|text|我知道这是有答案的。但我不认为，这是明确的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|214861|我想推荐以下几点。|214862|if+([[url1+absoluteString]+isEqualToString:[url2+absoluteString]])+
{
+++//Add+your+implementation+here
}|code-block|syntax|javascript|214863|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I know this is answered. But i don't think , its clear.

I would like to recommend the following.

<pre><code>if ([[url1 absoluteString] isEqualToString:[url2 absoluteString]]) 
{
 //Add your implementation here
}
</code></pre>

blocks|key|216896|text|我最近遇到过在比较两个URL(如https://www.google.com/和https://www.google.com+)时[NSURL+isEqual]方法返回false的情况，我发现将带有空字符串作为参数的URLByAppendingPathComponent应用于两个URL将返回正确的结果。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|216897|所以就像这样：|216898|[[urlOne+URLByAppendingPathComponent:@""]+isEqual:[urlTwo+URLByAppendingPathComponent:@""]]|code-block|syntax|javascript|216899|如果缺少则添加尾部斜杠，如果已包含则保持不变，因此比较将按预期进行。|216900|在我看来，我似乎依赖于一种奇怪的行为来工作-绕过另一种奇怪的行为，但这就是我要做的，除非我能被说服;-)|216901|entityMap^0|G|N|14|M|1T|F|30|R|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|14|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|R|$]]

Having recently encountered the situation where the <code>[NSURL isEqual]</code> method returns false when comparing two URLs like <code>https://www.google.com/</code> and <code>https://www.google.com</code> I have found that applying the <code>URLByAppendingPathComponent</code> with an empty-string as the parameter to both URLs will return the correct result.

So something like:

<pre><code>[[urlOne URLByAppendingPathComponent:@""] isEqual:[urlTwo URLByAppendingPathComponent:@""]]
</code></pre>

will add the trailing slash if missing and leave it alone if it is already included and so the comparison will work as expected.

Seems to me like I am relying on one strange behavior to work-around another strange behavior but this is what I am going with unless I can be convinced otherwise ;-).

I recently had a problem when comparing two NSURLs and compare one NSURL with an NSString(which is a URL address), the situation is I got an NSURLRequest from somewhere, I may or may not know the URL address it points to, and I have an URL NSString, say "http://m.google.com", now I need to check if the URL in that NSURLRequest is the same as the URL string I had:

<pre><code>[[request.URL.absoluteString lowercaseString] isEqualToString: [self.myAddress lowercaseString]];
</code></pre>

this returns NO as the <code>absoluteString</code> gives me "http://m.google.com/" whereas my string is "http://m.google.com" without a slash in the end, even if I create the NSURLRequest using

<pre><code>[NSURLRequest requestWithURL:[NSURL URLWithString:@"http://m.google.com"]]
</code></pre>

it still gives me "http://m.google.com/" for <code>absoluteString</code>, I wonder is there any reliable way to compare to NSURL or one NSURL and one NSString?

<ol>
<li>check if one 'contains' another, but this is not reliable as 'http://m.google.com/blabla' contains 'http://m.google.com'.</li>
<li>convert the NSString to NSURL and use the <code>isEqual</code> method to compare two NSURL and hopefully NSURL's implementation of <code>isEqual</code> can figure it out?</li>
<li>based on step 2, but convert each NSURL to a standard URL using <code>standardizedURL</code>?</li>
</ol>

Thanks a lot!

Reliable way to compare two NSURL or one NSURL and an NSString?

我最近在比较两个NSString和一个NSURLRequest (这是一个网址)时遇到了一个问题，情况是我从某个地方得到了一个NSString，我可能知道也可能不知道它指向的网址，我有一个URL，比如"，现在我需要检查该NSURLRequest中的URL是否与我拥有的URL字符串相同：[[request.URL.abs...

问比较两个NSURL或一个NSURL和一个NSString的可靠方法？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问比较两个NSURL或一个NSURL和一个NSString的可靠方法？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问比较两个NSURL或一个NSURL和一个NSString的可靠方法？
EN