dagrek

ColdFusion Variable is undefined in Session For the proper explanation of Session Fixation and how a session is undefined see http://www.petefreitag.com/item/815.cfm Watch out for the version of Coldfusion you are running and the hot fixes as there are differences http://www.bennadel.com/blog/2050-changes-in-cflocation-onrequestend-behavior-in-coldfusion-9-s-application-cfc.htm Session Fixation Bug (it's back to the old sessions lost after cflocation which was either introduced as a bug or fixed in CFMX6 ) "A JVM property was added in case you want to completely switch off the fix for the Session Fixation issue ( Bug 86378) which prior to this security release changed Session behavior in some environments. Add the following JVM property -Dcoldfusion.session.protectfixation=false in the JVM Arguments for the Coldfusion Server." http://helpx.adobe.com/coldfusion/kb/security-hotfix-coldfusion-8-8.html Programmatically can be fixed using the below: <cf

 Poodle and SSL 3.0, TLS 1.2  In order to fix the Poodle issue; SSL 3.0 needs to be disabled. You'll loose an odd ancient Browser or 2 but it's just not worth it. FYi, this also enables TLS 1.2 and 1.1. Other protocols that should not be round are PCT 1.0 and SSL 2.0 Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0\Server] "DisabledByDefault"=dword:00000001 "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client] "DisabledByDefault"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentContr

How to back up the IIS 7 Configuration Remember it used to be called a metabase? Open a command prompt with Run as Administrator then cd to %windir%\system32\inetsrv. appcmd add backup. The system will name it for you by using a date, time format and pop it in %windir%\system32\inetsrv\backup. Done.

So how to get your paypal invoicing set up? Login to the Paypal Sandbox with the account associated to your Paypal Invoicing Application (Google that, to find the latest URL!!) Click My Apps, create a new APP, save as draft and you will be ready to start testing. Note that when you are testing the Sandbox App Id is always APP-80W284485P519543T and the end point is https://svcs.sandbox.paypal.com/. You'll need approval from Paypal when finished testing!