You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The custom headers was really a nice addition to the project as you can bypass logins to many websites by simply adding the "header request" into ChangeDetection. Thank you for a nice tool.
Right now you can use custom headers when using Playwright Chromium (ws://playwright-chrome:3000') as a fetch, but like most header requests these expire after about 10-20 minutes and become useless shortly on websites that take bot detection seriously.
I think many users will want this feature and I am ready to sponsor it via BTC or Paypal into adoption, if you would like to add it to ChangeDetection.
What would be a nice add-on feature, is for the user to specify the 1st header requests so that ChangeDetection can reach the designated target, next to do a page refresh via "Execute Javascript" so it can grab brand new "header requests" from that page refresh and use these new headers on the next "detect" . This can be done in a loop, so every time you will have brand new "custom headers" on each request, therefore keeping the detect live for as long as you wish.
If you have a better idea in getting new "header requests" from each detect I would love to hear it.
Like I said I am ready to sponsor it into adoption, if you would consider introducing this very very useful feature to your already incredible tool.
Thank you and hope to hear from you soon.
The text was updated successfully, but these errors were encountered:
Hello everyone,
The custom headers was really a nice addition to the project as you can bypass logins to many websites by simply adding the "header request" into ChangeDetection. Thank you for a nice tool.
Right now you can use custom headers when using Playwright Chromium (ws://playwright-chrome:3000') as a fetch, but like most header requests these expire after about 10-20 minutes and become useless shortly on websites that take bot detection seriously.
I think many users will want this feature and I am ready to sponsor it via BTC or Paypal into adoption, if you would like to add it to ChangeDetection.
What would be a nice add-on feature, is for the user to specify the 1st header requests so that ChangeDetection can reach the designated target, next to do a page refresh via "Execute Javascript" so it can grab brand new "header requests" from that page refresh and use these new headers on the next "detect" . This can be done in a loop, so every time you will have brand new "custom headers" on each request, therefore keeping the detect live for as long as you wish.
If you have a better idea in getting new "header requests" from each detect I would love to hear it.
Like I said I am ready to sponsor it into adoption, if you would consider introducing this very very useful feature to your already incredible tool.
Thank you and hope to hear from you soon.
The text was updated successfully, but these errors were encountered: