aboutsummaryrefslogtreecommitdiffhomepage
path: root/Firebase/Database/Utilities/FStringUtilities.m
blob: dff58e047ada6acbcefba2b5c7f2a7642f1c3495 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
/*
 * Copyright 2017 Google
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

#import <CommonCrypto/CommonDigest.h>
#import "FStringUtilities.h"
#import "NSData+SRB64Additions.h"

@implementation FStringUtilities

// http://stackoverflow.com/questions/3468268/objective-c-sha1
// http://stackoverflow.com/questions/7310457/ios-objective-c-sha-1-and-base64-problem
+ (NSString *) base64EncodedSha1:(NSString *)str {
    const char *cstr = [str cStringUsingEncoding:NSUTF8StringEncoding];
    // NSString reports length in characters, but we want it in bytes, which strlen will give us.
    unsigned long dataLen = strlen(cstr);
    NSData *data = [NSData dataWithBytes:cstr length:dataLen];
    uint8_t digest[CC_SHA1_DIGEST_LENGTH];
    CC_SHA1(data.bytes, (unsigned int)data.length, digest);
    NSData* output = [[NSData alloc] initWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
    return [FSRUtilities base64EncodedStringFromData:output];
}

+ (NSString *) urlDecoded:(NSString *)url {
    NSString* replaced = [url stringByReplacingOccurrencesOfString:@"+" withString:@" "];
    NSString* decoded = [replaced stringByRemovingPercentEncoding];
    // This is kind of a hack, but is generally how the js client works. We could run into trouble if
    // some piece is a correctly escaped %-sequence, and another isn't. But, that's bad input anyways...
    if (decoded) {
        return decoded;
    } else {
        return replaced;
    }
}

+ (NSString *) urlEncoded:(NSString *)url {
    // Didn't seem like there was an Apple NSCharacterSet that had our version of the encoding
    // So I made my own, following RFC 2396 https://www.ietf.org/rfc/rfc2396.txt
    // allowedCharacters = alphanum | "-" | "_" | "~"
    NSCharacterSet *allowedCharacters = [NSCharacterSet characterSetWithCharactersInString:@"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-_~"];
    return [url stringByAddingPercentEncodingWithAllowedCharacters:allowedCharacters];
}

+ (NSString *) sanitizedForUserAgent:(NSString *)str {
    return [str stringByReplacingOccurrencesOfString:@"/|_" withString:@"|" options:NSRegularExpressionSearch range:NSMakeRange(0, [str length])];
}


@end