Change-Id: Ic4d1df0c4f7048a3e2472cca09ef9390bcfd149d
Reviewed-on: https://go-review.googlesource.com/4533Reviewed-by: Rob Pike <r@golang.org>

This change adds support for PROPFIND requests to net/webdav.
It contains a proposed PropSystem interface and a preliminary
implementation of an in-memory property system. As discussed
with nigeltao, this is the first of approximately 4-5 CLs to
get property support in the net/webdav package.

Current coverage of litmus 'props' test suite:
16 tests were skipped, 14 tests run. 10 passed, 4 failed. 71.4%

Change-Id: I0bc5f375422137e911a2f6fb0e99c43a5a52d5ac
Reviewed-on: https://go-review.googlesource.com/3417Reviewed-by: Nigel Tao <nigeltao@golang.org>

Change-Id: Ieba3be87526fab5fbc545735e0b721bfd5aea657
Reviewed-on: https://go-review.googlesource.com/7650Reviewed-by: Ian Lance Taylor <iant@golang.org>

Change-Id: I30996019437892e09bfe8710c903a510c96f5d13
Reviewed-on: https://go-review.googlesource.com/7619Reviewed-by: Ian Lance Taylor <iant@golang.org>

See golang.org/cl/4131 for context.

Change-Id: Iec4aa97042381e0ebb62f1361f3c71e3dee1c569
Reviewed-on: https://go-review.googlesource.com/7727Reviewed-by: David Crawshaw <crawshaw@golang.org>

Fixes golang/go#10164.

Change-Id: Ifcef660e4840cfcfa2f72a2be08541cad2b90440
Reviewed-on: https://go-review.googlesource.com/7611Reviewed-by: Minux Ma <minux@golang.org>

Fixes golang/go#10164.

Change-Id: I68b50ee4d516b3c9b6898e05b37a240f9592e19a
Reviewed-on: https://go-review.googlesource.com/7610Reviewed-by: Minux Ma <minux@golang.org>

Change-Id: I392835ac2ceddbdfc9f23e5a66abd16f7fd88b70
Reviewed-on: https://go-review.googlesource.com/6803Reviewed-by: Ian Lance Taylor <iant@golang.org>

Change-Id: I8a387f0fca0985c1ff059052173adee44dcdce90
Reviewed-on: https://go-review.googlesource.com/6804Reviewed-by: Ian Lance Taylor <iant@golang.org>

Change-Id: Ie5712a49f0c909538f4c36311b591e930a77efb5
Reviewed-on: https://go-review.googlesource.com/5410Reviewed-by: Andrew Gerrand <adg@golang.org>

The change to the standard encoding/xml library was
https://go-review.googlesource.com/#/c/2660/
which landed on 2015-02-14. An additional change was
https://go-review.googlesource.com/#/c/5910/ which
landed on 2015-03-03.

Fixes #9978.

Change-Id: I4f798f153e4e13b13eadc10e44b21a4b118251d3
Reviewed-on: https://go-review.googlesource.com/5714Reviewed-by: Nigel Tao <nigeltao@golang.org>

The current documentation as well as set of atoms and attributes has
gotten slightly out of sync with the current state of the WHATWG
html5 specification. The change adds and removes several of the atoms
and attributes, updates the documentation (such as steps numbering in
inBodyEndTagFormatting) and modifies the spec URLs to https://

Change-Id: I6dfa52785858c1521301b20b1e585e19a08b1e98
Reviewed-on: https://go-review.googlesource.com/6173Reviewed-by: Nigel Tao <nigeltao@golang.org>

This is necessary for cleanup of any goroutine that blocks on
ctx.Done(), as is done in e.g. propagateCancel in context.go. It is
already specified for WithTimeout and WithDeadline, whose descriptions I
have simplified here.

Change-Id: I6b30605decb8c0b7c1296c3f8852f9ad305ad4b7
Reviewed-on: https://go-review.googlesource.com/5022Reviewed-by: Sameer Ajmani <sameer@golang.org>

Change-Id: Ie44649d1d5594ba140e673eaafb94fecead561ee
Reviewed-on: https://go-review.googlesource.com/5214Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>

The current example leaks the DoSomethingSlow goroutine for an
arbitrarily long time.  In a real server, that can lead to an
out-of-memory failure during events such as network outages; a
more careful version of that example would be too long for a
simple package doc.

Fortunately, there are other short, common patterns using Done
that don't leak and don't require a lot of explanation.  Let's
use one of those instead.

Change-Id: I0ad0c6121d06b757a397e0e71be9e01ccfd75f77
Reviewed-on: https://go-review.googlesource.com/4490Reviewed-by: Andrew Gerrand <adg@golang.org>

This provides a CharsetReader function for xml.Decoder.

Change-Id: Id00787bbdee90d267d38c84c98a06f9e10d93336
Reviewed-on: https://go-review.googlesource.com/4420Reviewed-by: Nigel Tao <nigeltao@golang.org>

LockSystem.Confirm now takes two names (a src and a dst), and returns a
func() instead of a 1-method Releaser.

We now pass 25 of 30 "locks" litmus tests:
- 4 failures are due to PROPFIND / PROPPATCH not being implemented.
- 1 failure is due to shared locks being unsupported.
- 3 warnings are also due to PROPFIND / PROPPATCH.
- 1 failure (cond_put_corrupt_token) is due to returning 412
  (Precondition Failed) instead of 423 (Locked), but IIUC
  the spec says to return 412.
- 11 tests were skipped, presumably due to earlier failures.

Change-Id: I3f4c178cdc4b99c6acb7f59783b4fd9b94f606ec
Reviewed-on: https://go-review.googlesource.com/3860Reviewed-by: Dave Cheney <dave@cheney.net>

instead of FileSystem.Rename directly.

Dir.Rename's behavior wrt overwriting existing files and directories is
OS-dependent.

Fixes golang/go#9786

Change-Id: If42728caa6f0f38f8e3d6b1fcdda8c2d272080d6
Reviewed-on: https://go-review.googlesource.com/4341Reviewed-by: Nick Cooper <nmvc@google.com>
Reviewed-by: Alex Brainman <alex.brainman@gmail.com>

Change-Id: Iee673c97e6a3b779c3d8ba6bb1b5f2b2e2032b86
Reviewed-on: https://go-review.googlesource.com/3911Reviewed-by: Sameer Ajmani <sameer@golang.org>

This change implements ICMP extensions for interface and next-hop
identification which are used for route trace applications as described
in RFC 5837.

Change-Id: I2435109b5e766e743b894b0280a537324975489d
Reviewed-on: https://go-review.googlesource.com/3112Reviewed-by: Ian Lance Taylor <iant@golang.org>

The point of the DoSomething function is to protect the user from
DoSomethingSlow, which presumably doesn't support returning early upon
cancellation and deadline expiration (or else DoSomething wouldn't need
to exist).

Since most of the point of the Context object is communicating deadline
and cancellation, it is misleading for DoSomethingSlow to accept a
context object. A function like DoSomething is only likely to be written
when wrapping other code that doesn't properly support contexts.

Change-Id: Ibdef5b7ed71387ba6a09179ef2f911fc3f98e40a
Reviewed-on: https://go-review.googlesource.com/3902Reviewed-by: Sameer Ajmani <sameer@golang.org>

This change implements ICMP multi-part message marshaler, parser and
extensions for MPLS which are used for route trace applications as
described in RFC 4950.

API breaking changes:

type MessageBody interface, Len() int
type Extension interface, Len() int
type Extension interface, Marshal() ([]byte, error)

are replaced with

type MessageBody interface, Len(int) int
type Extension interface, Len(int) int
type Extension interface, Marshal(int) ([]byte, error)

Change-Id: Iee1f2e03916d49b8dfe3a89fe682c702d40ecc85
Reviewed-on: https://go-review.googlesource.com/2794Reviewed-by: Ian Lance Taylor <iant@golang.org>

Change-Id: I86f0c7695b7888c9cfed4386734cce9f0e05e3fd
Reviewed-on: https://go-review.googlesource.com/3982Reviewed-by: David Symonds <dsymonds@golang.org>

Change-Id: Idcd7c225efda94021ba18ca33f3fe7e8565140fe
Reviewed-on: https://go-review.googlesource.com/3861Reviewed-by: Dave Cheney <dave@cheney.net>
Reviewed-by: Nick Cooper <nmvc@google.com>

Forbidden during copyFiles.

Change-Id: Ica2df08e1e4086c0c6db5a4c90bcf4fefc850bc7
Reviewed-on: https://go-review.googlesource.com/3835Reviewed-by: Dave Cheney <dave@cheney.net>

http://golang.org/pkg/net/http/#ResponseWriter says that "Changing the
header after a call to WriteHeader (or Write) has no effect."

Change-Id: Ica749e1475a93d535adb1300bc599d5cfe49a94f
Reviewed-on: https://go-review.googlesource.com/3689Reviewed-by: Nick Cooper <nmvc@google.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>

This helps line up HTTP events (in the Go code) with the litmus test
suite (C code).

Change-Id: I2d0847069ae1304948ba1219b63cd438a4fa921c
Reviewed-on: https://go-review.googlesource.com/3760Reviewed-by: Robert Stepanek <robert.stepanek@gmail.com>
Reviewed-by: Nick Cooper <nmvc@google.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>

Change-Id: I285f93e562ca0c6bdc6168e6c47b28c7caef7cf5
Reviewed-on: https://go-review.googlesource.com/3501Reviewed-by: Nick Cooper <nmvc@google.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>

Change-Id: I22d47bc4a07911a8c7c57a2db83f5c8ffe1c420c
Reviewed-on: https://go-review.googlesource.com/3565Reviewed-by: Nick Cooper <nmvc@google.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>

just new files.

Section 10.5 says the Lock-Token applies when creating a new lock, not
just when (implicitly) creating a new file.

The litmus test expects this.

Change-Id: I8746154c9baba9a90b4e9db79cadb6839fc170c7
Reviewed-on: https://go-review.googlesource.com/3567Reviewed-by: Dave Cheney <dave@cheney.net>

Change-Id: I1d91ddf7fb4eebd4782f0621446ec2820d132788
Reviewed-on: https://go-review.googlesource.com/3562Reviewed-by: Ian Lance Taylor <iant@golang.org>

Change-Id: If1243dd2d79824933d896a8c4b31db8c247d0c21
Reviewed-on: https://go-review.googlesource.com/3561Reviewed-by: Ian Lance Taylor <iant@golang.org>

These occur after a heap.Remove call, and heap.Remove calls
byExpiry.Pop, which already sets n.byExpiryIndex to -1.

The memLS.consistent method in lock_test.go checks that the expiry
fields are all consistent.

Change-Id: I09f5d02999e4635f15d1723f89a86b951ed95950
Reviewed-on: https://go-review.googlesource.com/3563Reviewed-by: Dave Cheney <dave@cheney.net>
Reviewed-by: Nick Cooper <nmvc@google.com>

Also add a -port flag to litmus_test_server.

13 of 13 copymove tests from the litmus suite pass, as does 16 of 16
basic tests.

Change-Id: Idf92cad281e15db7d4d62e28e366ea7bfa89e564
Reviewed-on: https://go-review.googlesource.com/3470Reviewed-by: Nick Cooper <nmvc@google.com>
Reviewed-by: Robert Stepanek <robert.stepanek@gmail.com>
Reviewed-by: Nigel Tao <nigeltao@golang.org>

Change-Id: I0e4245c26f2a19b366cd22fabefa8d0e65c6b2cc
Reviewed-on: https://go-review.googlesource.com/3560Reviewed-by: Dave Cheney <dave@cheney.net>

Change-Id: I12b41d16b49415081242e06b25a7106a4a0c0442
Reviewed-on: https://go-review.googlesource.com/3402Reviewed-by: Ian Lance Taylor <iant@golang.org>

Change-Id: I3cf716c9ae02d7daa0d5a11249c3b58f6c8be2fe
Reviewed-on: https://go-review.googlesource.com/3403Reviewed-by: Ian Lance Taylor <iant@golang.org>

Change-Id: I06585ba7e40c1653139520f3d67d96e5d86302ac
Reviewed-on: https://go-review.googlesource.com/3401Reviewed-by: Ian Lance Taylor <iant@golang.org>

This change copies a few code fragments from
https://golang.org/cl/13422044.

Change-Id: I7ceae3a59e15dc9f9ef4b2b64a41753aa9d6798b
Reviewed-on: https://go-review.googlesource.com/3400Reviewed-by: Ian Lance Taylor <iant@golang.org>

This change contains a proposal for marshalling multistatus responses to
support the lock and property systems. In addition, a type for properties
is defined for the to-be-implemented property system.

Change-Id: I3d768d8d61bb9495bc70e4699dee8958d444147f
Reviewed-on: https://go-review.googlesource.com/3160Reviewed-by: Nigel Tao <nigeltao@golang.org>