Closed johnkdoe closed 9 years ago
didn't run into it in live code, but encountered this statement when was doing a blanket cleanup in our company-wide project that uses CocoaSPDY as a sub-project . i don't know if it's possible for HTTPMethod to return nil … in my blunt-instrument approach, it just seemed best to nil-check it. i can live without the change if the API for HTTPMethod guarantees never to return nil …
if s is nil, then [s caseInsensitiveComapre:a] will return 0, and 0 is the same as NSOrderedSame, so this equality check incorrectly results in YES (!!)