Redirect with modified request

masumbuet · October 29, 2018, 10:41pm

Hi,
I am creating a plugin. When user tries to visit a website, I want to validate the user and then redirect back to the original domain once validated. I tried to set a Header in the request to indicate the user is validated and then http.Redirect using status code 302. But when I receive the request after redirecting, the Header field is not there. How can I achieve this?

Whitestrake · October 29, 2018, 11:07pm

Just to clarify, you had your server send a response header to the client alongside the redirect, and the problem is that the client didn’t return that header on subsequent requests?

masumbuet · October 29, 2018, 11:54pm

Yes. I don’t see the header I set when I receive the request after redirect.

Whitestrake · October 30, 2018, 12:09am

Unless the header in question is Cookie, I don’t believe any client would have cause to repeat a header back to the server after receiving it, unless it was programmed to do so.

magikstm · November 1, 2018, 3:31am

loginsrv does that (GitHub - tarent/loginsrv: JWT login microservice with plugable backends such as OAuth2, Google, Github, htpasswd, osiam, ..).

This may help: loginsrv/redirect.go at master · tarent/loginsrv · GitHub

github.com

tarent/loginsrv/blob/master/login/handler.go#L254

    
      
          		return
          	}
          
          
	if wantHTML(r) {
          		h.respondAuthenticatedHTML(w, r, token)
          		return
          	}
          
          
	w.Header().Set("Content-Type", contentTypeJWT)
          	w.WriteHeader(200)
          	fmt.Fprint(w, token)
          }
          
          
func (h *Handler) respondAuthenticatedHTML(w http.ResponseWriter, r *http.Request, token string) {
          	cookie := &http.Cookie{
          		Name:     h.config.CookieName,
          		Value:    token,
          		HttpOnly: h.config.CookieHTTPOnly,
          		Path:     "/",
          	}
          	if h.config.CookieExpiry != 0 {

masumbuet · November 1, 2018, 3:50pm

But the line looks like it is updating the response header, not the request header.

system · January 30, 2019, 3:50pm

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.