Getting 301 errors since end of March

[huubvanh]

Hi, I use your great delay webhook function for home automation but face an issue since end of March.

In the logging of my ifttt applet when posting a new delay I can see a 301 error.
When I just call the URL via postman its okay.

Is this a known issue/bug or did I miss an update to apply in my applet?

Thanks in advance for the reply!

[grapeot]

Thanks for reporting this! I upgraded my server in the end of March and that's probably the reason of why you saw a 301. But a 301 is not really an error. It's telling the browser that the page has been permanently moved and requesting the browser to follow the redirection. From the backend I don't see a drop on the success rate but I may be missing something. Curious did you see the action being executed after the delay? I guess not? Did you use an http or an https endpoint? If it's the former, I may know what is the reason and will help change the server configuration. If it's the latter, I will need to do more investigation. Thanks, Yan

…

________________________________ From: huubvanh ***@***.***> Sent: Saturday, April 9, 2022 00:50 To: grapeot/IFTTTDelay ***@***.***> Cc: Subscribed ***@***.***> Subject: [grapeot/IFTTTDelay] Getting 301 errors since end of March (Issue #6) Hi, I use your great delay webhook function for home automation but face an issue since end of March. In the logging of my ifttt applet when posting a new delay I can see a 301 error. When I just call the URL via postman its okay. Is this a known issue/bug or did I miss an update to apply in my applet? Thanks in advance for the reply! — Reply to this email directly, view it on GitHub<#6>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAM4XC72NJPKXB27NHJLOMLVEEZE3ANCNFSM5S6TJ5AA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[huubvanh]

Hi, thanks for the quick response! In the first applet I turn on ventilation and as final action register the delay via:
https://lab.grapeot.me/ifttt/delay?event=VentOff90Min&t=90&key=mykey

[grapeot]

Ah this is very helpful. This is because I upgraded the security settings in the end of March to enforce https. And when one visits the old http URL, the browser will receive a 301 so it knows to automatically redirect to the https URL. It seems to work with most of the IFTTT requests according to my monitoring after the upgrade, but looks it may fail the IFTTT in some cases. In your case, can you change the http in your URL to https? So it would look like this: https://lab.grapeot.me/ifttt/delay?event=VentOff90Min&t=90&key=mykey. (Your comment shows https but the screenshot shows http. So I assume the comment may actually be http.)

[huubvanh]

Sorry, I changed to https and its working again. Sorry for waisting your time.
Best regards, Huub

[grapeot]

Glad to see it's resolved! No no no it's not wasting my time at all. Thanks for letting me know the problem and putting it as a GitHub issue. So others may also benefit from it.

…

________________________________ From: huubvanh ***@***.***> Sent: Sunday, April 10, 2022 1:40:49 AM To: grapeot/IFTTTDelay ***@***.***> Cc: Yan Wang ***@***.***>; Comment ***@***.***> Subject: Re: [grapeot/IFTTTDelay] Getting 301 errors since end of March (Issue #6) Sorry, I changed to https and its working again. Sorry for waisting your time. Best regards, Huub — Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAM4XC7B6KFGF6LIEBQLTADVEKHZDANCNFSM5S6TJ5AA>. You are receiving this because you commented.Message ID: ***@***.***>