gin

gin copied to clipboard

Error struct custom ？

1

JellyZero

## Description In handler function, I write the code `c.Error(xxxx)`. I want to test the function, but r.serveHTTP(w, c.Request) doesn't affect the test gin context c, error array of c.Errors...

sixwaaaay

fix Request.Context() checks

11

Fixes nil pointer dereference panic introduced here: https://github.com/gin-gonic/gin/pull/3172 Closes https://github.com/gin-gonic/gin/issues/3343 Closes https://github.com/gin-gonic/gin/issues/3581 Closes https://github.com/gin-gonic/gin/issues/3483 Closes https://github.com/gin-gonic/gin/issues/3178 `c.engine.ContextWithFallback` check panics in `Deadline()`, `Done()`, `Err()` and `Value()` when `c.engine` is `nil`. ---...

bvidosits

fix lack of escaping of filename in Content-Disposition

10

https://github.com/gin-gonic/gin/issues/3555

motoyasu-saburi

FileAttachment() is vulnerable to Reflect File Download

2

I have contacted the maintainer 4-5 times via email, Snyk, etc., but have not received a reply, so I am raising an Issue. ## Description `gin` > `context.go` > `func...

motoyasu-saburi

Remove redundant code

1

Remove redundant code `engine.RouterGroup.engine = engine` the `RouterGroup` can remove.

youngxhui

Panic in context .Value() When Key Not Found and .engine is nil

2

## Description After upgrading to 1.9.0 (from 1.5.0), our test code is now crashing here in `context.go` line 1216: ``` if !c.engine.ContextWithFallback || c.Request == nil || c.Request.Context() == nil...

jcburley

Context.HTML: Missing template import causes panic

2

## Description If you forget to import a template, you get a panic - shouldn't this be caught and a useful message printed to the console? (at least in debug...

voltagex

It's a backward-compatible update that let users skip logs based on customized logic. Gin's `LoggerConfig` only allows configuring `SkipPaths`. It might not be enough when users need to skip logging...

palvaneh

change function type to pointer receivers error

1

Struct Error has methods on both value and pointer receivers. Such usage is not recommended by the Go Documentation.

aliheydarabadii