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

Redirect test misses #185

Closed
ietf-svn-bot opened this issue Jun 30, 2007 · 7 comments
Closed

Redirect test misses #185

ietf-svn-bot opened this issue Jun 30, 2007 · 7 comments

Comments

@ietf-svn-bot
Copy link

owner:[email protected] resolution_fixed type_defect | by [email protected]


The buildbot shows two redirect test misses -- these are maybe OK, but should be checked and fixed if needed or the test updated if no fix neede.

Miss 301 /public/ipr_generic.cgi?command=update_ipr&ipr_id=657 ->
         /ipr/new-generic/?ipr_id=657&command=update_ipr
 (wanted /ipr/update/657/)
         2007-06-30_14:57 +0s

Miss 301 /public/pidtracker.cgi?command=view_id&dTag=12689&rfc_flag=0 ->
         /idtracker/rfc12689/
 (wanted /idtracker/12689/)
         2007-06-30_14:57 +0s

Issue migrated from trac:185 at 2022-03-04 00:45:49 +0000

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Second is a bug in my fix for #178, fixed in 9059da0.

First seems to just be a missing entry in the redirects fixture - a new test added without a corresponding fixture entry?

@ietf-svn-bot
Copy link
Author

@[email protected] changed status from new to assigned

@ietf-svn-bot
Copy link
Author

@[email protected] changed owner from `` to [email protected]

@ietf-svn-bot
Copy link
Author

@[email protected] commented


First one points out that all 3 ipr cgis need redirects and testurls.

@ietf-svn-bot
Copy link
Author

@[email protected] changed status from assigned to closed

@ietf-svn-bot
Copy link
Author

@[email protected] changed resolution from `` to fixed

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Fixed in 0f08671

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant