chaitin / lua-resty-t1k Goto Github PK

配置如下

location / {
            mirror /mirror;
            proxy_pass $backend_protocol://backend;
        }

        location = /mirror {
		internal;
        	access_by_lua_block {
            		local t1k = require "resty.t1k"

            		local t = {
                		mode = "block",
                		host = "10.2.0.63",
                		port = 8000,
            		}

            		local ok, err, result = t1k.do_access(t, true)
            		if not ok then
                		ngx.log(ngx.ERR, err)
            		end
        	}

        	header_filter_by_lua_block {
            		local t1k = require "resty.t1k"
            		t1k.do_header_filter()
        	}

        	content_by_lua_block {
            		ngx.say("passed")
        	}
    	}

但是未生效

Hello, everyone! Greetings! I'm the developer of the lua-resty-t1k project. Ever since its release, I've seen some great work done by the community. People have written beginner tutorials and even developed their own Golang/Java SDKs based on the T1K protocol. It has brought us immense joy.

Now, internally, we do have Golang, Java, and Python SDKs, but let's be honest, SDKs aren't our top priority, and our Java framework expertise is a bit rusty. It's been a while since we had a master maintaining it. For instance, we attempted to create a Spring Boot Interceptor using the Java SDK, but without real business scenarios, we weren't sure about the end result.

That's why we're counting on the power of the community to enrich and improve the T1K SDK series.

Feel free to create T1K SDKs/Filters/Plugins/Interceptors, or anything related to lua-resty-t1k, in any language, framework, or even a proxy. You can create a corresponding repo under your own account, or you can "donate" the repo to the Chaitin organization, so more people can see your work and find potential collaborators.

Additionally, we're on the hunt for long-term Maintainers for the Golang/Java SDKs. We want to optimize and maybe even refactor the SDKs to enhance their performance.

We welcome everyone to express their interests and the directions they'd like to contribute to in this issue. You can also share the scenarios where you think the T1K protocol would be applicable.

例如 将一个恶意SQL注入请求发送到safeline以后，resty-t1k 可以获取到该请求的拦截原因，拦截类型等数据。

openresty出现点问题想单独卸载这个模块测试下原因