mirror of
https://github.com/tailscale/tailscale.git
synced 2026-02-09 01:32:09 +01:00
3ec5be3f51
This file was never truly necessary and has never actually been used in the history of Tailscale's open source releases. A Brief History of AUTHORS files --- The AUTHORS file was a pattern developed at Google, originally for Chromium, then adopted by Go and a bunch of other projects. The problem was that Chromium originally had a copyright line only recognizing Google as the copyright holder. Because Google (and most open source projects) do not require copyright assignemnt for contributions, each contributor maintains their copyright. Some large corporate contributors then tried to add their own name to the copyright line in the LICENSE file or in file headers. This quickly becomes unwieldy, and puts a tremendous burden on anyone building on top of Chromium, since the license requires that they keep all copyright lines intact. The compromise was to create an AUTHORS file that would list all of the copyright holders. The LICENSE file and source file headers would then include that list by reference, listing the copyright holder as "The Chromium Authors". This also become cumbersome to simply keep the file up to date with a high rate of new contributors. Plus it's not always obvious who the copyright holder is. Sometimes it is the individual making the contribution, but many times it may be their employer. There is no way for the proejct maintainer to know. Eventually, Google changed their policy to no longer recommend trying to keep the AUTHORS file up to date proactively, and instead to only add to it when requested: https://opensource.google/docs/releasing/authors. They are also clear that: > Adding contributors to the AUTHORS file is entirely within the > project's discretion and has no implications for copyright ownership. It was primarily added to appease a small number of large contributors that insisted that they be recognized as copyright holders (which was entirely their right to do). But it's not truly necessary, and not even the most accurate way of identifying contributors and/or copyright holders. In practice, we've never added anyone to our AUTHORS file. It only lists Tailscale, so it's not really serving any purpose. It also causes confusion because Tailscalars put the "Tailscale Inc & AUTHORS" header in other open source repos which don't actually have an AUTHORS file, so it's ambiguous what that means. Instead, we just acknowledge that the contributors to Tailscale (whoever they are) are copyright holders for their individual contributions. We also have the benefit of using the DCO (developercertificate.org) which provides some additional certification of their right to make the contribution. The source file changes were purely mechanical with: git ls-files | xargs sed -i -e 's/\(Tailscale Inc &\) AUTHORS/\1 contributors/g' Updates #cleanup Change-Id: Ia101a4a3005adb9118051b3416f5a64a4a45987d Signed-off-by: Will Norris <will@tailscale.com>
65 lines
2.2 KiB
Go
65 lines
2.2 KiB
Go
// Copyright (c) Tailscale Inc & contributors
|
|
// SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
package tsweb
|
|
|
|
import (
|
|
"encoding/json"
|
|
"strings"
|
|
"time"
|
|
)
|
|
|
|
// AccessLogRecord is a record of one HTTP request served.
|
|
type AccessLogRecord struct {
|
|
// Timestamp at which request processing started.
|
|
Time time.Time `json:"time"`
|
|
// Time it took to finish processing the request. It does not
|
|
// include the entire lifetime of the underlying connection in
|
|
// cases like connection hijacking, only the lifetime of the HTTP
|
|
// request handler.
|
|
Seconds float64 `json:"duration,omitempty"`
|
|
|
|
// The client's ip:port.
|
|
RemoteAddr string `json:"remote_addr,omitempty"`
|
|
// The HTTP protocol version, usually "HTTP/1.1 or HTTP/2".
|
|
Proto string `json:"proto,omitempty"`
|
|
// Whether the request was received over TLS.
|
|
TLS bool `json:"tls,omitempty"`
|
|
// The target hostname in the request.
|
|
Host string `json:"host,omitempty"`
|
|
// The HTTP method invoked.
|
|
Method string `json:"method,omitempty"`
|
|
// The unescaped request URI, including query parameters.
|
|
RequestURI string `json:"request_uri,omitempty"`
|
|
|
|
// The client's user-agent
|
|
UserAgent string `json:"user_agent,omitempty"`
|
|
// Where the client was before making this request.
|
|
Referer string `json:"referer,omitempty"`
|
|
|
|
// The HTTP response code sent to the client.
|
|
Code int `json:"code,omitempty"`
|
|
// Number of bytes sent in response body to client. If the request
|
|
// was hijacked, only includes bytes sent up to the point of
|
|
// hijacking.
|
|
Bytes int `json:"bytes,omitempty"`
|
|
// Error encountered during request processing.
|
|
Err string `json:"err,omitempty"`
|
|
// RequestID is a unique ID for this request. If the *http.Request context
|
|
// carries this value via SetRequestID, then it will be displayed to the
|
|
// client immediately after the error text, as well as logged here. This
|
|
// makes it easier to correlate support requests with server logs. If a
|
|
// RequestID generator is not configured, RequestID will be empty.
|
|
RequestID RequestID `json:"request_id,omitempty"`
|
|
}
|
|
|
|
// String returns m as a JSON string.
|
|
func (m AccessLogRecord) String() string {
|
|
if m.Time.IsZero() {
|
|
m.Time = time.Now()
|
|
}
|
|
var buf strings.Builder
|
|
json.NewEncoder(&buf).Encode(m)
|
|
return strings.TrimRight(buf.String(), "\n")
|
|
}
|