Timeline for What is the correct pipeline to process redirection logic
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 19 at 8:00 | comment | added | ckhanna | @sukesh Since you are redirecting right, so this can be done at the initial stage rather than doing in the later stages since you do want those processors to be executed once the redirection has happened... | |
| Sep 19 at 7:57 | comment | added | sukesh |
Should the custom code be patched before Sitecore.Pipelines.HttpRequest.IgnoreList or Sitecore.Pipelines.HttpRequest.ItemResolver
|
|
| Sep 19 at 7:22 | history | edited | ckhanna | CC BY-SA 4.0 |
edited body
|
| Sep 19 at 7:02 | comment | added | ckhanna |
@sukesh I just updated the answer below where the pipline to be placed in the httpRequestBegin pipeline to avoid the issue you are getting. Let me know in case you have any queries.
|
|
| Sep 19 at 7:00 | history | edited | ckhanna | CC BY-SA 4.0 |
added 525 characters in body
|
| Sep 18 at 13:27 | comment | added | ckhanna | ya I dont see any reason of moving it to httpRequestBegin pipeline because this will be getting triggered only after preprocessrequest pipeline. If we can abort the execution at the first level only, then the second level wont get even triggered and can prevent the issue you are getting..Hope that makes sense!!! | |
| Sep 18 at 13:22 | comment | added | sukesh |
Would this be a better approach than moving the pipeline to httpRequestBegin?
|
|
| Sep 18 at 12:36 | history | answered | ckhanna | CC BY-SA 4.0 |