1. 11 Sep, 2016 9 commits
  2. 10 Sep, 2016 12 commits
  3. 09 Sep, 2016 18 commits
  4. 08 Sep, 2016 1 commit
    • Dave Day's avatar
      net/url: handle escaped paths in ResolveReference · f27c1bda
      Dave Day authored
      Currently, path resolution is done using the un-escaped version of
      paths. This means that path elements like one%2ftwo%2fthree are
      handled incorrectly, and optional encodings (%2d vs. -) are dropped.
      
      This function makes escaped handling consistent with Parse: provided
      escapings are honoured, and RawPath is only set if necessary.
      
      A helper method setPath is introduced to handle the correct setting of
      Path and RawPath given the encoded path.
      
      Fixes #16947
      
      Change-Id: I40b1215e9066e88ec868b41635066eee220fde37
      Reviewed-on: https://go-review.googlesource.com/28343
      Run-TryBot: Dave Day <djd@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarBrad Fitzpatrick <bradfitz@golang.org>
      f27c1bda