Skip to content

En/http redirects #1640

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

Open
wants to merge 28 commits into
base: development
Choose a base branch
from
Open

En/http redirects #1640

wants to merge 28 commits into from

Conversation

Umang01-hash
Copy link
Member

@Umang01-hash Umang01-hash commented Apr 10, 2025

Pull Request Template

Description:

Example:

package main

import (
	"gofr.dev/pkg/gofr"

	"gofr.dev/pkg/gofr/http/response"
)

func main() {
	app := gofr.New()

	app.GET("/old-page", func(ctx *gofr.Context) (any, error) {
		// Redirect to a new URL 
		return response.Redirect{URL: "https://example.com/new-page"}, nil
	})

	app.Run()
}
Screenshot 2025-04-10 at 1 15 45 PM

Additional Information:

  • Mention any relevant dependencies or external libraries used.
  • Include screenshots or code snippets (if necessary) to clarify the changes.

Checklist:

  • I have formatted my code using goimport and golangci-lint.
  • All new code is covered by unit tests.
  • This PR does not decrease the overall code coverage.
  • I have reviewed the code comments and documentation for clarity.

Thank you for your contribution!

@coolwednesday
Copy link
Contributor

coolwednesday commented Apr 10, 2025

@Umang01-hash , Can we also check and add tests for url with path and query params as well as request Bodies, headers etc.....get handled successfully through the redirect. I feel that is not the case right now.

@coolwednesday
Copy link
Contributor

@Umang01-hash , Can we also check and add tests for url with path and query params as well as request Bodies, headers etc.....get handled successfully through the redirect. I feel that is not the case right now.

@Umang01-hash, Can we add test for these cases ? I feel this implementation can fall short in fitting these usecases.

Copy link
Contributor

@ccoVeille ccoVeille left a comment

Choose a reason for hiding this comment

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

@Umang01-hash Umang01-hash requested a review from ccoVeille May 6, 2025 08:10
Comment on lines +7 to +12
// NewRedirect creates a redirect response with the specified URL and status code.
func NewRedirect(url string) Redirect {
return Redirect{
URL: url,
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

This can be removed.

Copy link
Contributor

Choose a reason for hiding this comment

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

Good catch

Comment on lines +7 to +12
// NewRedirect creates a redirect response with the specified URL and status code.
func NewRedirect(url string) Redirect {
return Redirect{
URL: url,
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Good catch

Comment on lines 32 to 34
var resp any

switch v := data.(type) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Nitpicking, there are no need to update this, especially if we consider it diverges from Go standards

Suggested change
var resp any
switch v := data.(type) {
var resp any
switch v := data.(type) {

Comment on lines +51 to +57
case resTypes.Redirect:
switch r.method {
case http.MethodPost, http.MethodPut, http.MethodPatch:
statusCode = http.StatusSeeOther // 303
default:
statusCode = http.StatusFound // 302 by default
}
Copy link
Contributor

Choose a reason for hiding this comment

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

🎨 style

Suggested change
case resTypes.Redirect:
switch r.method {
case http.MethodPost, http.MethodPut, http.MethodPatch:
statusCode = http.StatusSeeOther // 303
default:
statusCode = http.StatusFound // 302 by default
}
case resTypes.Redirect:
// HTTP 302 by default
statusCode = http.StatusFound
switch r.method {
case http.MethodPost, http.MethodPut, http.MethodPatch:
// HTTP 303
statusCode = http.StatusSeeOther
}

Comment on lines +51 to +57
case resTypes.Redirect:
switch r.method {
case http.MethodPost, http.MethodPut, http.MethodPatch:
statusCode = http.StatusSeeOther // 303
default:
statusCode = http.StatusFound // 302 by default
}
Copy link
Contributor

Choose a reason for hiding this comment

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

There is something I cannot explain: why we computed this line 30

         statusCode, errorObj := r.determineResponse(data, err)

And we here don't care about statusCode we computed

Shouldn't we check if data.type is not redirect before calling determineResponse ? And so redirect without calling it

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.

How to Perform Redirects in Gofr?
5 participants