hanzoai/ingress
2
0
Fork 0
mirror of https://github.com/hanzoai/ingress.git synced 2026-10-26 02:47:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
v1.7.x
ingress/pkg/server/service
T
History
zeekay 13a0ac68f7 feat(zap-backend): log [ZAP-BACKEND] line on each ZAP-routed request 
Drops a structured log line whenever a request is routed through the
ZAP-HTTP transport instead of the wrapped net/http transport. Operators
can confirm wire-level routing with:

  kubectl logs deploy/liquid-ingress | grep ZAP-BACKEND
2026-05-06 18:47:47 -07:00
..
loadbalancer
feat: reset module path to hanzoai/ingress v1 (was v3)
2026-04-12 13:00:48 -07:00
tcp
feat: reset module path to hanzoai/ingress v1 (was v3)
2026-04-12 13:00:48 -07:00
udp
feat: reset module path to hanzoai/ingress v1 (was v3)
2026-04-12 13:00:48 -07:00
internalhandler.go
Fix internal handlers ServiceBuilder composition
2024-11-19 14:52:04 +01:00
managerfactory.go
feat: reset module path to hanzoai/ingress v1 (was v3)
2026-04-12 13:00:48 -07:00
service_test.go
feat: reset module path to hanzoai/ingress v1 (was v3)
2026-04-12 13:00:48 -07:00
service.go
feat: reset module path to hanzoai/ingress v1 (was v3)
2026-04-12 13:00:48 -07:00
smart_roundtripper.go
feat: reset module path to hanzoai/ingress v1 (was v3)
2026-04-12 13:00:48 -07:00
transport_test.go
feat: reset module path to hanzoai/ingress v1 (was v3)
2026-04-12 13:00:48 -07:00
transport.go
feat(transport): ZAP-HTTP backend transport (env-allowlisted)
2026-05-06 13:36:02 -07:00
zap_backend_test.go
feat(transport): ZAP-HTTP backend transport (env-allowlisted)
2026-05-06 13:36:02 -07:00
zap_backend.go
feat(zap-backend): log [ZAP-BACKEND] line on each ZAP-routed request
2026-05-06 18:47:47 -07:00