Web form error 308 Permanent Redirect


(Marc Winkelman) #1

Problem connecting to CRM through web form post URLs. Our vendor is using an automated system to post data to the web form post urls for 2 separate lead funnels. They are receiving the error:

"The remote server returned an error: (308) Permanent Redirect "

How to resolve and InfusionSoft tech support apparently does not support API questions even as they may have done something internally to cause this new issue.


(Mike Wozniak) #2

We have the same exact problem, and it is acknowledged on the http://knownissues.infusionsoft.com/ page. I checked in with support and there are no updates.

Our form post integrations have worked for YEARS and we are deeply disappointed in whatever change Infusionsoft has made to break these. Now some of our business logic can’t run and it is causing a huge inconvenience to several of our companies.

Can Infusionsoft support provide an update on this known issue?


(Abram Pousada) #3

We found that we can “get by” for now using CURL, as the known issue documented suggested. However, this appears to have appears to have a side-effect of the forms being posted twice for some reason. Here’s an example of a CURL command we used:

curl --location --cookie-jar "[path-to/cookiejar.txt]" --data "[post-data]" --header "Content-Type: application/x-www-form-urlencoded" --request POST "[form-url]"

You can also add an argument like -trace "[path-to/trace.txt]" to see the details of what’s going on behind the scenes, and it’s mind boggling. We opened up a support ticket with an extensive amount of detail in hopes that it helps push things forward on this matter.


(Eric Seguin) #4

Any updates on this? All I’m trying to do is HTTP Post to a webform and get this error every time on multiple campaigns. The HTTP post has the inf_form_xid, the inf_form_name, and infusionsoft_version.
That’s another question…does the infusionsoft version of the webform have to be there? The reason i’m asking is that every other day the webform’s version changes, so I would think that the HTTP posts would also have to be updated with that version number to work?


(Tina Lei) #5

We have the same issue. Not sure when did they make the change, but I’m pretty sure it was working around June. Contacted the support team several time, they never understand what’s going on. So disappointed. According to their known issues recommendation, for http post a form, it’s better to user api. But if we switch to api, the web form triggered campaign will stop working, right?