Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proxy middleware: reuse echo request context #2537

Merged
merged 1 commit into from
Nov 5, 2023

Conversation

x1h0
Copy link
Contributor

@x1h0 x1h0 commented Oct 27, 2023

I have used the proxy middleware in one of my projects and need the context values in modifyResponse, which I had set before in my custom balancer.
Unfortunately, I had to realise that the context does not seem to be taken over and there is no option to get it.
With this change, the context from http.Request is reused.

If there is an alternative way to get the previous request context, please tell me.

@TomKrouss
Copy link

I have run into a similar problem, any update (either on the change or an alternative) would be appreciated.

@x1h0
Copy link
Contributor Author

x1h0 commented Nov 2, 2023

Hi @aldas, could you please check this PR?

@@ -359,6 +359,10 @@ func ProxyWithConfig(config ProxyConfig) echo.MiddlewareFunc {
c.Set("_error", nil)
}

// Reuse context from echo request
// This is needed to access context values in modifyResponse.
req = req.WithContext(c.Request().Context())

This comment was marked as outdated.

This comment was marked as outdated.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, I think I see your point.

package main

import (
	"context"
	"github.com/labstack/echo/v4"
	"github.com/labstack/echo/v4/middleware"
	"github.com/stretchr/testify/assert"
	"net/http"
	"net/http/httptest"
	"net/url"
	"testing"
)

type customBalancer struct {
	target *middleware.ProxyTarget
}

func (b *customBalancer) AddTarget(target *middleware.ProxyTarget) bool {
	panic("not implemented")
	return true
}

func (b *customBalancer) RemoveTarget(name string) bool {
	panic("not implemented")
	return false
}

func (b *customBalancer) Next(c echo.Context) *middleware.ProxyTarget {
	ctx := context.WithValue(c.Request().Context(), "FROM_BALANCER", "CUSTOM_BALANCER")
	c.SetRequest(c.Request().WithContext(ctx))
	return b.target
}

func TestModifyResponseUseContext(t *testing.T) {
	server := httptest.NewServer(
		http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
			w.WriteHeader(http.StatusOK)
			w.Write([]byte("OK"))
		}),
	)
	defer server.Close()

	targetURL, _ := url.Parse(server.URL)

	e := echo.New()
	e.Use(middleware.ProxyWithConfig(
		middleware.ProxyConfig{
			Balancer: &customBalancer{
				target: &middleware.ProxyTarget{
					Name: "tst",
					URL:  targetURL,
				},
			},
			RetryCount: 1,
			ModifyResponse: func(res *http.Response) error {
				val := res.Request.Context().Value("FROM_BALANCER")
				if valStr, ok := val.(string); ok {
					res.Header.Set("FROM_BALANCER", valStr)
				}
				return nil
			},
		},
	))

	req := httptest.NewRequest(http.MethodGet, "/", nil)
	rec := httptest.NewRecorder()

	e.ServeHTTP(rec, req)

	assert.Equal(t, http.StatusOK, rec.Code)
	assert.Equal(t, "OK", rec.Body.String())
	assert.Equal(t, "CUSTOM_BALANCER", rec.Header().Get("FROM_BALANCER"))
}

Is it something like that?

Copy link
Contributor

@aldas aldas Nov 4, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe

				// This is needed for ProxyConfig.ModifyResponse and/or ProxyConfig.Transport to be able to process the Request
				// that Balancer may have replaced with c.SetRequest.
				req = c.Request()
  1. This comment says why and where if line is useful.
  2. do we need req = req.WithContext() at all we could just retake that pointer (pointing to new request instance) from echo.Context?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also - please add at least one test

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @aldas,

thanks for your review. I have adjusted the PR according to your comments.

Is it something like that?

Yes, your test does exactly what I am trying to do.

This comment says why and where if line is useful.

I have adopted the comment.

do we need req = req.WithContext() at all we could just retake that pointer (pointing to new request instance) from echo.Context?

No, we don't need it. Your suggestion req = c.Request() is perfectly adequate.

also - please add at least one test

I have adopted your test and fixed the context key lint error. Is that okay?

Copy link

codecov bot commented Nov 5, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (69a0de8) 92.88% compared to head (27a8c74) 92.89%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2537   +/-   ##
=======================================
  Coverage   92.88%   92.89%           
=======================================
  Files          39       39           
  Lines        4655     4658    +3     
=======================================
+ Hits         4324     4327    +3     
  Misses        240      240           
  Partials       91       91           
Files Coverage Δ
middleware/proxy.go 74.75% <100.00%> (+0.38%) ⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@aldas aldas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@aldas aldas merged commit c7d6d43 into labstack:master Nov 5, 2023
16 checks passed
@aldas
Copy link
Contributor

aldas commented Nov 5, 2023

I will look if we have some other PRs to merge and maybe do a patch release containing this PR.

@aldas aldas mentioned this pull request Nov 7, 2023
@aldas
Copy link
Contributor

aldas commented Nov 7, 2023

New version is out: https://github.com/labstack/echo/releases/tag/v4.11.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants