BeeRock v1.2 Release
Note:
- The uploaded builds in this release are not signed. Your OS will likely not be happy with it. Please see Install Instructions.
- The uploaded *.zip files are "self-contained" builds and you do not need to install .NET 7. Convenient, but makes the build bigger.
New in BeeRock v1.2
-
(experimental) Added support for proxying http requests
- call
<<bee.Proxy.ForwardToServer("https://mytargetserver")>>
to forward the request another server - call
<<bee.Proxy.ForwardToUrl("https://mytargetserver")>>
to forward the request, fully specifying the target url
Note: HTTP request and response headers are copied from when requests are proxied
- call
-
Added support for logging from python scripts
- call
<<bee.Log.Info("message")>>
to log an info message - call
<<bee.Log.Error("message")>>
to log an error message - call
<<bee.Log.Warn("message")>>
to log a warning message - call
<<bee.Log.NewLine()>>
to log an empty new line
- call
-
Added support for bypassing swagger schema validations on responses
- call
<<bee.Context.Response.SetAsPassThrough()>>
to indicate that the response should not be validated against the swagger schema - call
<<bee.Context.Response.SetContentType("contentType")>>
to manually specify the content type of the response - call
<<bee.Context.Response.SetStatusCode(int:statusCode)>>
to manually specify the status code type of the response
For example:
- call
-
Added support to manually control the http request and response headers
- Get a header
Ex.<<headers.Request.Get("key")>>
Ex.<<headers.Response.Get("key")>>
- Add or overwrite a header
Ex.<<headers.Request.Add("key", "value")>>
Ex.<<headers.Response.Add("key", "value")>>
- Remove a header
Ex. <<headers.Request.Remove("key")>>
Ex.<<headers.Response.Remove("key")>>
- Get a header
-
Improved logging to included proxied http responses
-
UI fixes