>> We've got a 3rd party API that we call via HTTPS. They >> want the >> data submitted via GET (i.e. URL strings) whereas its my >> understanding that POST would be more secure. Am I >> correct in >> my understanding or loosing my mind?
> You are incorrect, but I doubt you're losing your mind. > When you make an > HTTPS request, the entire request (including the URL > you're requesting) is > encrypted. So, they are equally secure. For that matter, > they're equally > secure within plain old HTTP - both are perfectly readable > plaintext. > However, variables within a URL are easily observed by the > user of a > browser, so in that sense they are more likely to be > tinkered with by the > user. Although in this case I'm betting he's using cfhttp or some equivalent and no browser will see those url variables. s. isaac dealey 954.522.6080 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://www.fusiontap.com http://coldfusion.sys-con.com/author/4806Dealey.htm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:213124 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
