Changed query argument order in testurls to agree with the order produced by the redirects. Accompanying new acceptable diff file.
- Legacy-Id: 481
This commit is contained in:
parent
d7c5b248e9
commit
e4deb27623
|
@ -1,19 +1,19 @@
|
|||
# -*- conf-mode -*-
|
||||
200 /ipr/ https://datatracker.ietf.org/public/ipr_list.cgi
|
||||
200 /ipr/ipr-657/ https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=657 # Generic disclosure
|
||||
200 /ipr/ipr-834/ https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=834 # Specific disclosure
|
||||
200 /ipr/ipr-795/ https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=795 # Third-party disclosure
|
||||
200 /ipr/new-generic/ https://datatracker.ietf.org/public/ipr_generic.cgi
|
||||
200 /ipr/new-specific/ https://datatracker.ietf.org/public/ipr.cgi
|
||||
200 /ipr/new-third-party/ https://datatracker.ietf.org/public/ipr_notify.cgi
|
||||
200 /ipr/update/ https://datatracker.ietf.org/public/ipr_update_list.cgi
|
||||
200 /ipr/search/ https://datatracker.ietf.org/public/ipr_search.cgi
|
||||
302 /ipr/search/?option=document_search # incomplete argument set gives redirect
|
||||
200 /ipr/search/?option=document_search&document_search=mod https://datatracker.ietf.org/public/ipr_search.cgi?option=document_search&document_search=mod
|
||||
200,sort /ipr/search/?option=document_search&id_document_tag=2220 https://datatracker.ietf.org/public/ipr_search.cgi?option=document_search&id_document_tag=2220
|
||||
200,sort /ipr/search/?option=rfc_search&rfc_search=1034 https://datatracker.ietf.org/public/ipr_search.cgi?option=rfc_search&rfc_search=1034 # Loong result, RFC search
|
||||
200 /ipr/search/?option=rfc_search&rfc_search=4444 https://datatracker.ietf.org/public/ipr_search.cgi?option=rfc_search&rfc_search=4444 # Empty result, RFC search
|
||||
200 /ipr/about/ https://datatracker.ietf.org/public/ipr_disclosure.cgi
|
||||
200 /ipr/2006/
|
||||
200 /ipr/2006/feb/
|
||||
200 /ipr/by-date/
|
||||
200 /ipr/ https://datatracker.ietf.org/public/ipr_list.cgi
|
||||
200 /ipr/ipr-657/ https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=657 # Generic disclosure
|
||||
200 /ipr/ipr-834/ https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=834 # Specific disclosure
|
||||
200 /ipr/ipr-795/ https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=795 # Third-party disclosure
|
||||
200 /ipr/new-generic/ https://datatracker.ietf.org/public/ipr_generic.cgi
|
||||
200 /ipr/new-specific/ https://datatracker.ietf.org/public/ipr.cgi
|
||||
200 /ipr/new-third-party/ https://datatracker.ietf.org/public/ipr_notify.cgi
|
||||
200 /ipr/update/ https://datatracker.ietf.org/public/ipr_update_list.cgi
|
||||
200 /ipr/search/ https://datatracker.ietf.org/public/ipr_search.cgi
|
||||
302 /ipr/search/?option=document_search # incomplete argument set gives redirect
|
||||
200 /ipr/search/?document_search=mod&option=document_search https://datatracker.ietf.org/public/ipr_search.cgi?option=document_search&document_search=mod
|
||||
200,sort /ipr/search/?id_document_tag=2220&option=document_search https://datatracker.ietf.org/public/ipr_search.cgi?option=document_search&id_document_tag=2220
|
||||
200,sort /ipr/search/?rfc_search=1034&option=rfc_search https://datatracker.ietf.org/public/ipr_search.cgi?option=rfc_search&rfc_search=1034 # Loong result, RFC search
|
||||
200 /ipr/search/?rfc_search=4444&option=rfc_search https://datatracker.ietf.org/public/ipr_search.cgi?option=rfc_search&rfc_search=4444 # Empty result, RFC search
|
||||
200 /ipr/about/ https://datatracker.ietf.org/public/ipr_disclosure.cgi
|
||||
200 /ipr/2006/
|
||||
200 /ipr/2006/feb/
|
||||
200 /ipr/by-date/
|
||||
|
|
26
test/diff/_ipr_search__rfc_search-1034&option=rfc_search
Normal file
26
test/diff/_ipr_search__rfc_search-1034&option=rfc_search
Normal file
|
@ -0,0 +1,26 @@
|
|||
--- https://datatracker.ietf.org/public/ipr_search.cgi?option=rfc_search&rfc_search=1034
|
||||
+++ /ipr/search/?rfc_search=1034&option=rfc_search
|
||||
@@ -148,1 +148,1 @@
|
||||
-Search result on RFC1035, "Domain names - implementation and specification", that was updated by RFC3658, "Delegation Signer Resource Record"
|
||||
+Search result on RFC1035, "Domain names - implementation and specification", that was updated by RFC4033, "DNS Security Introduction and Requirements"
|
||||
@@ -171,2 +171,2 @@
|
||||
-Search result on RFC2181, "Clarifications to the DNS Specification", that updated RFC1035, "Domain names - implementation and specification"
|
||||
-Search result on RFC2308, "Negative Caching of DNS Queries (DNS NCACHE)", that updated RFC1035, "Domain names - implementation and specification"
|
||||
+Search result on RFC2181, "Clarifications to the DNS Specification", that was updated by RFC4035, "Protocol Modifications for the DNS Security Extensions"
|
||||
+Search result on RFC2308, "Negative Caching of DNS Queries (DNS NCACHE)", that was updated by RFC4035, "Protocol Modifications for the DNS Security Extensions"
|
||||
@@ -188,2 +188,2 @@
|
||||
-Search result on RFC3008, "Domain Name System Security (DNSSEC) Signing Authority", that was obsoleted by RFC4033, "DNS Security Introduction and Requirements"
|
||||
-Search result on RFC3090, "DNS Security Extension Clarification on Zone Status", that was obsoleted by RFC4035, "Protocol Modifications for the DNS Security Extensions"
|
||||
+Search result on RFC3008, "Domain Name System Security (DNSSEC) Signing Authority", that was updated by RFC3658, "Delegation Signer Resource Record"
|
||||
+Search result on RFC3090, "DNS Security Extension Clarification on Zone Status", that was updated by RFC3658, "Delegation Signer Resource Record"
|
||||
@@ -201,2 +201,2 @@
|
||||
-Search result on RFC3658, "Delegation Signer Resource Record", that updated RFC3090, "DNS Security Extension Clarification on Zone Status"
|
||||
-Search result on RFC3755, "Legacy Resolver Compatibility for Delegation Signer", that updated RFC3658, "Delegation Signer Resource Record"
|
||||
+Search result on RFC3658, "Delegation Signer Resource Record", that was updated by RFC3755, "Legacy Resolver Compatibility for Delegation Signer"
|
||||
+Search result on RFC3755, "Legacy Resolver Compatibility for Delegation Signer", that was updated by RFC3845, "DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format"
|
||||
@@ -204,1 +204,1 @@
|
||||
-Search result on RFC3845, "DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format", that updated RFC3755, "Legacy Resolver Compatibility for Delegation Signer"
|
||||
+Search result on RFC3845, "DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format", that was obsoleted by RFC4035, "Protocol Modifications for the DNS Security Extensions"
|
||||
@@ -206,1 +206,1 @@
|
||||
-Search result on RFC4034, "Resource Records for the DNS Security Extensions", that obsoleted RFC3008, "Domain Name System Security (DNSSEC) Signing Authority"
|
||||
+Search result on RFC4034, "Resource Records for the DNS Security Extensions", that updated RFC2136, "Dynamic Updates in the Domain Name System (DNS UPDATE)"
|
Loading…
Reference in a new issue