Re: [PATCH] Document the HTTP transport protocols

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx> writes:

>  This is basically the version from Tay Ray Chuan [1] with one more
>  proofreading round from me. My changes besides realignments are below.
>  There are TODOs remain but I think the document is valuable as it is.

Thanks.

>  On the topic, C Git's (maybe) violations on this spec are:
>  
>   - The client does not strip trailing slashes from $GIT_URL before
>     sending to the server, as described in section "URL Format".
>  
>   - The client does not check that HTTP status code is either 200 or
>     304 when receiving response in discovering references phase.
>
>   - The client verifies the first 5 bytes against pattern
>     "^[0-9a-fA-F]{4}#" instead of "^[0-9a-f]{4}#" as described in
>     section "discovering references".

Perhaps add these to "small projects ideas"?  The last one may want
to be phrased a bit better, though.  I needed to read it twice to
realize that you are saying "the client accepts hexadecimal using
uppercase alphabets where it should not".
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]