Skip to content

G
go
Switch branch/tag
  1. 18 Oct, 2011 12 commits
  3. 17 Oct, 2011 17 commits
  5. 16 Oct, 2011 2 commits
  7. 15 Oct, 2011 5 commits
    • Anthony Martin's avatar
      goyacc: clean up after units · fc61ea3b
      Anthony Martin authored 
      R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5286047
      fc61ea3b
    • Alex Brainman's avatar
      syscall: dll function load and calling changes · 78479163
      Alex Brainman authored 
      New DLL and Proc types to manage and call dll functions. These were
used to simplify syscall tests in runtime package. They were also
used to implement LazyDLL and LazyProc.

LazyProc, like Proc, now have Call function, that just a wrapper for
SyscallN. It is not as efficient as Syscall, but easier to use.

NewLazyDLL now supports non-ascii filenames.

LazyDLL and LazyProc now have Load and Find methods. These can be used
during runtime to discover if some dll functions are not present.

All dll functions now return errors that fit os.Error interface. They
also contain Windows error number.

Some of these changes are suggested by jp.

R=golang-dev, jp, rsc
CC=golang-dev
https://golang.org/cl/5272042
      78479163
    • Andrew Balholm's avatar
      html: improve parsing of comments and "bogus comments" · b770c9e9
      Andrew Balholm authored 
      R=nigeltao
CC=golang-dev
https://golang.org/cl/5279044
      b770c9e9
    • Brad Fitzpatrick's avatar
      http: DoS protection: cap non-Handler Request.Body reads · 5079129d
      Brad Fitzpatrick authored 
      Previously, if an http.Handler didn't fully consume a
Request.Body before returning and the request and the response
from the handler indicated no reason to close the connection,
the server would read an unbounded amount of the request's
unread body to advance past the request message to find the
next request's header. That was a potential DoS.

With this CL there's a threshold under which we read
(currently 256KB) in order to keep the connection in
keep-alive mode, but once we hit that, we instead
switch into a "Connection: close" response and don't
read the request body.

Fixes #2093 (along with number of earlier CLs)

R=golang-dev, dsymonds
CC=golang-dev
https://golang.org/cl/5268043
      5079129d
    • Anthony Martin's avatar
      http: avoid panic caused by nil URL · b5077f82
      Anthony Martin authored 
      The current code will panic if an invalid
request (one with a nil URL) is passed to
the doFollowingRedirects function.

Also, remove a redundant nil Header check.

R=bradfitz
CC=golang-dev
https://golang.org/cl/5270046
      b5077f82
  9. 14 Oct, 2011 4 commits
    • Robert Griesemer's avatar
      godoc: updates for latest Go app-engine release. · c5b3a4fb
      Robert Griesemer authored 
      R=adg
CC=golang-dev
https://golang.org/cl/5273044
      c5b3a4fb
    • Andrew Gerrand's avatar
      doc: add go-tour-kr, a Korean translation of A Tour of Go · 92b7b482
      Andrew Gerrand authored 
      R=golang-dev, dsymonds
CC=golang-dev
https://golang.org/cl/5273043
      92b7b482
    • Dave Cheney's avatar
      godefs: add enum/const testdata · a3ff67c3
      Dave Cheney authored 
      Also, add golden output data for linux/arm.

R=golang-dev, rsc
CC=golang-dev
https://golang.org/cl/5256041
      a3ff67c3
    • Chris Farmiloe's avatar
      xml: match Marshal's XMLName behavior in Unmarshal · 55751a38
      Chris Farmiloe authored 
      When xml.Marshal is called on a struct it will happily
reflect the information in the "tag" of an XMLName member
regardless of the type to give the struct a tag-name in
it's XML form. This is backed up by the documentation which
says:

However xml.Unmarshal *does* care about the XMLName field
being of type xml.Name, and currently returns the error
"field XMLName does not have type xml.Name" if you have it
set to something else.

This is firstly inconsistant with xml.Marshal but it also
makes it impossible to use xml.Marshal alongside other
Marshallers (like json/bson) without poluting the state's
namespace with XMLName fields. Inorder to exclude fields
from other Marshallers the convention has been started to
tag fields as "omitempty"; which will cause the field not
to display if it is at it's "zero" state, XMLName cannot
have such as zero-state since it is a struct, so it is nicer
to use a pointer/bool value for XMLName so it can be easily
excluded when I want to Marshal my struct by some other
wire format.

Attached is the proposed minor change, that simply stops
erring if it can't set the name on the XMLName field, which
is just optional metadata anyway.
Fixes #2265.

R=rsc
CC=golang-dev
https://golang.org/cl/5067044
      55751a38
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7