Question
MX8 CFHTTP Bug
I believe I found a bug with the CFHTTP tag in CF8. I have a
CFHTTP post call being made within a loop through a list of URL's
(multiple servers). I exit out of the loop upon a successful
CFHTTP.StatusCode indicator (200 or 202 status codes). This logic
has been working this way for years in CF5, 7 & 8.
Just the other day we upgraded our SSL certificate on one of the CF5 servers this CF8 page is communicating to via this CFHTTP loop logic. The new SSL cert is not recognized by our JRE and the POST to this server results in the following error: HTTP ERROR: Connection Failure. Status code unavailable.
I already know why the SSL cert is unrecognized and I'll be correcting that BUT the loop logic found a side effect I believe to be a bug. In looping through to the next URL, the formfields in the POST are double posted. By "double post," I mean if I indended to post USERNAME=Joe123, the second action page in the url list receives USERNAME=Joe123,Joe123 -- this is for all the form fields.
I have not determined if this is always the case and have just not noticed or if this is specifically related to the SSL failure. Below is a snippet of my code. This snippet has been simplified for this example so there might be a typo, but hopefully it will convey the issue:
Just the other day we upgraded our SSL certificate on one of the CF5 servers this CF8 page is communicating to via this CFHTTP loop logic. The new SSL cert is not recognized by our JRE and the POST to this server results in the following error: HTTP ERROR: Connection Failure. Status code unavailable.
I already know why the SSL cert is unrecognized and I'll be correcting that BUT the loop logic found a side effect I believe to be a bug. In looping through to the next URL, the formfields in the POST are double posted. By "double post," I mean if I indended to post USERNAME=Joe123, the second action page in the url list receives USERNAME=Joe123,Joe123 -- this is for all the form fields.
I have not determined if this is always the case and have just not noticed or if this is specifically related to the SSL failure. Below is a snippet of my code. This snippet has been simplified for this example so there might be a typo, but hopefully it will convey the issue:
