Golang invalid character ‘\x00‘ after top-level value

最新推荐文章于 2023-12-25 20:26:56 发布

Sinkmist

最新推荐文章于 2023-12-25 20:26:56 发布

阅读量3w

点赞数

分类专栏： Go 文章标签： golang

本文链接：https://blog.csdn.net/qq_40601372/article/details/107712820

版权

Golang invalid character ‘\x00’ after top-level value

文章目录

Golang invalid character '\x00' after top-level value

1 概述

当我们无法无法判断需要创建的字节切片A的长度的时候，通常会创建一个较大长度的空字节切片B来接收未知长度的字节，当使用json.Unmarshal解析字节的时候，就会出现 panic invalid character ‘\x00’ after top-level value 的错误，这是因为B切片的长度实际大于A所需的长度，Json读取到nil的时候，会停止继续读取，造成多出一个\x00，而json无法解析\x00

错误日志

2020/07/31 13:44:14 [Recovery] 2020/07/31 - 13:44:14 panic recovered:
POST /price HTTP/1.1
Host: localhost:8080
Accept: */*
Accept-Encoding: gzip, deflate, br
Cache-Control: no-cache
Connection: keep-alive
Content-Length: 133
Content-Type: application/json
Postman-Token: 97f9e99a-4e28-4d3b-a241-372efbcf4ee4
User-Agent: PostmanRuntime/7.26.2


invalid character '\x00' after top-level value
D:/Library/Code/Projects/cloud-price/main.go:23 (0xa9a0ee)
	main.func1: panic(err)
C:/Users/Mist/go/pkg/mod/github.com/gin-gonic/gin@v1.6.3/context.go:161 (0xa7a91f)
	(*Context).Next: c.handlers[c.index](c)
C:/Users/Mist/go/pkg/mod/github.com/gin-gonic/gin@v1.6.3/recovery.go:83 (0xa96ca7)
	RecoveryWithWriter.func1: c.Next()
C:/Users/Mist/go/pkg/mod/github.com/gin-gonic/gin@v1.6.3/context.go:161 (0xa7a91f)
	(*Context).Next: c.handlers[c.index](c)
C:/Users/Mist/go/pkg/mod/github.com/gin-gonic/gin@v1.6.3/logger.go:241 (0xa9578b)
	LoggerWithConfig.func1: c.Next()
C:/Users/Mist/go/pkg/mod/github.com/gin-gonic/gin@v1.6.3/context.go:161 (0xa7a91f)
	(*Context).Next: c.handlers[c.index](c)
C:/Users/Mist/go/pkg/mod/github.com/gin-gonic/gin@v1.6.3/gin.go:409 (0xa878bb)
	(*Engine).handleHTTPRequest: c.Next()
C:/Users/Mist/go