-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timezone parsing errors / misbehavior #34
Comments
Related to this, in the example curl statement used to show how ubbagent is used, it looks like this:
This produces output like This date format string works:
|
Date parsing errors make the HTTP agent very unhappy, it instantly closes the connection and returns nothing (not even HTTP 400*)
|
Remove usage of '%N' in example `date` commands since it's not supported by some platforms. #34
Regarding the timezone parsing error: this is a really horrible error message generated by Go's time library when parsing a timestamp in RFC3339 format. The "07:00" text comes from the format described here: https://github.com/golang/go/blob/master/src/time/format.go#L78. The message is basically telling you that a timezone is required: either "Z" or something like "+07:00". I'll see if I can wrap this in a more meaningful message. The '%N' in the example curl command adds nanoseconds. I guess this is platform-dependent (and assume you're using OS X?). I've removed '%N' from the example commands. And regarding the HTTP response: I'm not able to reproduce the closed connection. I get a 500 on parse error which, while not ideal, is at least a response, and is what I would expect given this line: https://github.com/GoogleCloudPlatform/ubbagent/blob/master/http/http.go#L56. Is the closed connection always reproducible for you? |
Sample input (as
t.json
)Posting this:
Assuming timezone UTC (
Z
) would have made sense, but not sure where the 07:00 offset is coming from, this looks like a bug.The text was updated successfully, but these errors were encountered: