onHttpRequestHeaders 返回 types.HeaderStopIteration 后阻塞，没有执行到 onHttpRequestBody || onHttpRequestHeaders blocks after returning types.HeaderStopIteration and does not execute onHttpRequestBody

[guodoliu]

描述：目前有个场景，需要读取请求体，然后修改请求头，但是在onHttpRequestHeaders 返回return types.HeaderStopIteration，日志显示阻塞住，没有执行到 onHttpRequestBody，180s 后 stream timeout
代码：package main

import (
"encoding/json"
"strings"

"github.com/alibaba/higress/plugins/wasm-go/pkg/wrapper"
"github.com/higress-group/proxy-wasm-go-sdk/proxywasm"
"github.com/higress-group/proxy-wasm-go-sdk/proxywasm/types"

)

const (
DefaultMaxBodyBytes = 10 * 1024 * 1024 // 100MB
)

func main() {
wrapper.SetCtx(
"test",
wrapper.ParseConfigBy(config.ParseConfig),
wrapper.ProcessRequestHeadersBy(onHttpRequestHeaders),
wrapper.ProcessRequestBodyBy(onHttpRequestBody),
)
}

func onHttpRequestHeaders(ctx wrapper.HttpContext, config config.TestConfig, log wrapper.Log) types.Action {
log.Debugf("onHttpRequestHeaders")
if !wrapper.HasRequestBody() {
ctx.DontReadRequestBody()
return types.ActionContinue
}

contentType, _ := proxywasm.GetHttpRequestHeader("content-type")
if contentType == "" {
	ctx.DontReadRequestBody()
	return types.ActionContinue
}

if !strings.Contains(contentType, "application/json") {
	log.Debugf("content-type is not application/json")
	ctx.DontReadRequestBody()
	return types.ActionContinue
}

// 10MB buffer limit
ctx.SetRequestBodyBufferLimit(DefaultMaxBodyBytes)
return types.HeaderStopIteration

}

func onHttpRequestBody(ctx wrapper.HttpContext, config config.TestConfig, body []byte, log wrapper.Log) types.Action {
log.Debugf("onHttpRequestBody")

return handleJsonBody(ctx, config, body, log)

}

func handleJsonBody(ctx wrapper.HttpContext, config config.TestConfig, body []byte, log wrapper.Log) types.Action {
log.Debugf("hanlde json body")
if !json.Valid(body) {
log.Error("invalid json body")
return types.ActionContinue
}

return types.ActionContinue

}

go 依赖：
go 1.19

require (
github.com/alibaba/higress/plugins/wasm-go v1.4.4-0.20250225053732-e27d3d097168
github.com/higress-group/proxy-wasm-go-sdk v1.0.1
github.com/higress-group/wasm-go v1.1.1
github.com/tidwall/gjson v1.18.0
github.com/tidwall/resp v0.1.1
github.com/wasilibs/go-re2 v1.5.3
golang.org/x/time v0.11.0
)

require (
github.com/google/uuid v1.6.0 // indirect
github.com/higress-group/nottinygc v0.0.0-20231101025119-e93c4c2f8520 // indirect
github.com/magefile/mage v1.14.0 // indirect
github.com/tetratelabs/wazero v1.7.2 // indirect
github.com/tidwall/match v1.1.1 // indirect
github.com/tidwall/pretty v1.2.1 // indirect
github.com/tidwall/sjson v1.2.5 // indirect
)

higress 运行版本： v2.0.7

---

Description: There is currently a scenario where the request body needs to be read and then the request headers modified. However, onHttpRequestHeaders returns return types.HeaderStopIteration. The log shows that it is blocked and onHttpRequestBody is not executed. The stream timeout occurs after 180s.
Code: package main

import (
"encoding/json"
"strings"

"github.com/alibaba/higress/plugins/wasm-go/pkg/wrapper"
"github.com/higress-group/proxy-wasm-go-sdk/proxywasm"
"github.com/higress-group/proxy-wasm-go-sdk/proxywasm/types"

)

const (
DefaultMaxBodyBytes = 10 * 1024 * 1024 // 100MB
)

func main() {
wrapper.SetCtx(
"test",
wrapper.ParseConfigBy(config.ParseConfig),
wrapper.ProcessRequestHeadersBy(onHttpRequestHeaders),
wrapper.ProcessRequestBodyBy(onHttpRequestBody),
)
}

func onHttpRequestHeaders(ctx wrapper.HttpContext, config config.TestConfig, log wrapper.Log) types.Action {
log.Debugf("onHttpRequestHeaders")
if !wrapper.HasRequestBody() {
ctx.DontReadRequestBody()
return types.ActionContinue
}

contentType, _ := proxywasm.GetHttpRequestHeader("content-type")
if contentType == "" {
	ctx.DontReadRequestBody()
	return types.ActionContinue
}

if !strings.Contains(contentType, "application/json") {
	log.Debugf("content-type is not application/json")
	ctx.DontReadRequestBody()
	return types.ActionContinue
}

// 10MB buffer limit
ctx.SetRequestBodyBufferLimit(DefaultMaxBodyBytes)
return types.HeaderStopIteration

}

func onHttpRequestBody(ctx wrapper.HttpContext, config config.TestConfig, body []byte, log wrapper.Log) types.Action {
log.Debugf("onHttpRequestBody")

return handleJsonBody(ctx, config, body, log)

}

func handleJsonBody(ctx wrapper.HttpContext, config config.TestConfig, body []byte, log wrapper.Log) types.Action {
log.Debugf("hanlde json body")
if !json.Valid(body) {
log.Error("invalid json body")
return types.ActionContinue
}

return types.ActionContinue

}

go dependencies:
go 1.19

require (
github.com/alibaba/higress/plugins/wasm-go v1.4.4-0.20250225053732-e27d3d097168
github.com/higress-group/proxy-wasm-go-sdk v1.0.1
github.com/higress-group/wasm-go v1.1.1
github.com/tidwall/gjson v1.18.0
github.com/tidwall/resp v0.1.1
github.com/wasilibs/go-re2 v1.5.3
golang.org/x/time v0.11.0
)

require (
github.com/google/uuid v1.6.0 // indirect
github.com/higress-group/nottinygc v0.0.0-20231101025119-e93c4c2f8520 // indirect
github.com/magefile/mage v1.14.0 // indirect
github.com/tetratelabs/wazero v1.7.2 // indirect
github.com/tidwall/match v1.1.1 // indirect
github.com/tidwall/pretty v1.2.1 // indirect
github.com/tidwall/sjson v1.2.5 // indirect
)

higress running version: v2.0.7

[CH3CHO]

You can update following dependencies to the given versions, and remove the dependency to github.com/alibaba/higress/plugins/wasm-go then see if it works:

	github.com/higress-group/proxy-wasm-go-sdk v0.0.0-20251103120604-77e9cce339d2
	github.com/higress-group/wasm-go v1.0.10-0.20260120033417-1c84f010156d

[guodoliu]

更新依赖库版本后使用tinygo 编译报错tinygo build -scheduler=none -target=wasi -gc=custom -tags='custommalloc nottinygc_finalizer'
-o out/plugin.wasm
extensions/test/main.go
panic: missing core function "runtime.free"

goroutine 149 [running]:
github.com/tinygo-org/tinygo/transform.Optimize({0xc00b6cfdd8?}, 0xc00030c1b0, 0x2, 0x100386439?, 0x5)
/Users/runner/work/tinygo/tinygo/transform/optimizer.go:70 +0xdf5
github.com/tinygo-org/tinygo/builder.optimizeProgram({0x7fb058a051b0?}, 0xc00030c1b0)
/Users/runner/work/tinygo/tinygo/builder/build.go:1068 +0x13f
github.com/tinygo-org/tinygo/builder.Build.func5(0xc00b694fc0)
/Users/runner/work/tinygo/tinygo/builder/build.go:572 +0x61d
github.com/tinygo-org/tinygo/builder.runJob(0xc00b695020, 0x1046f5220?)
/Users/runner/work/tinygo/tinygo/builder/jobs.go:222 +0x4d
created by github.com/tinygo-org/tinygo/builder.runJobs in goroutine 1
/Users/runner/work/tinygo/tinygo/builder/jobs.go:123 +0x5bd

[CH3CHO]

BTW, how do you send the test request?

[guodoliu]

curl --location 'http://xxx.xcc.ccc'
--header 'Content-Type: application/json'
--header 'Authorization: Bearer $API_KEY'
--data '{
"model": "http_server",
"messages": [
{
"role": "system",
"content": "你是XX，是由开发的 AI 人工智能助手."
},
{
"role": "user",
"content": "常见的十字花科植物有哪些？"
}
]
}'

---

curl --location 'http://xxx.xcc.ccc'
--header 'Content-Type: application/json'
--header 'Authorization: Bearer $API_KEY'
--data '{
"model": "http_server",
"messages": [
{
"role": "system",
"content": "You are XX, an AI artificial intelligence assistant developed by."
},
{
"role": "user",
"content": "What are the common cruciferous plants?"
}
]
}'

[guodoliu]

我好想知道原因了，tinygo 编译的时候需要添加 EXTRA_TAGS=proxy_wasm_version_0_2_100 才会生效

---

I really want to know the reason. When compiling tinygo, you need to add EXTRA_TAGS=proxy_wasm_version_0_2_100 for it to take effect

[CH3CHO]

我好想知道原因了，tinygo 编译的时候需要添加 EXTRA_TAGS=proxy_wasm_version_0_2_100 才会生效

是的。

---

I really want to know the reason. When compiling tinygo, you need to add EXTRA_TAGS=proxy_wasm_version_0_2_100 for it to take effect.

Yes.

[CH3CHO]

2.1.4 以后的版本就可以直接用 GO 编译了，不需要加这个标识。

---

Versions after 2.1.4 can be compiled directly with GO, and there is no need to add this mark.

[guodoliu]

了解了，感谢大佬

---

Got it, thank you boss