- 23 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
Currently the HTTP handlers are attached to an API mux which is created inside Setup(). In the future, we'll want to split this out so a single mux can have both sync and clientapi handlers attached to it.
-
- 22 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 18 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
* Update gomatrixserverib dep * Use helper functions when creating rooms * Use gomatrixserverlib.StateKeyTuple
-
- 17 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 15 3月, 2017 2 次提交
- 13 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 11 3月, 2017 3 次提交
-
-
由 Kegsay 提交于
-
由 Kegsay 提交于
Previously, the error responses: - were not valid matrix errors (no `errcode`) - returned the `err.Error()` message which may contain sensitive information. - did not get logged (at all, let alone set the level correctly). Now the error responses: - return valid matrix errors (`M_UNKNOWN`) - return a generic "Internal Server Error" string - get logged at `ERROR` level.
-
由 Kegsay 提交于
-
- 10 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 09 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 08 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 07 3月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 24 2月, 2017 1 次提交
-
-
由 Kegsay 提交于
-
- 21 2月, 2017 2 次提交
-
-
由 Kegsay 提交于
Terse function names are used to make usage not stutter. For example: ```go err := error.Forbidden("you shall not pass") ``` At the moment they are all the same fundamental `MatrixError` type. This will be bad if we ever want to `switch` based on the kind of error. I'm hoping we won't ever need to introspect into errors like this: ideally these errors would be created purely for immediately being returned in an HTTP response. `MatrixError` implements the `error` interface.
-
由 Kegsay 提交于
-
- 20 2月, 2017 1 次提交
-
-
由 Kegsay 提交于
* Add basic routing based on matched paths * Make /sync and /send use the right API paths
-
- 04 2月, 2017 3 次提交
-
-
由 Kegan Dougal 提交于
-
由 Kegan Dougal 提交于
-
由 Kegan Dougal 提交于
As per RL discussion with Mjark
-