Status/Resolution/Reason: Closed/Withdrawn/NotABug
Reporter/Name(from Bugbase): Craig Kaminsky / Craig Kaminsky (craigkaminsky)
Created: 09/07/2012
Components: Installation/Config
Versions: 10.0
Failure Type: Enhancement Request
Found In Build/Fixed In Build: Final /
Priority/Frequency: Trivial / Unknown
Locale/System: English / Platforms All
Vote Count: 1
I want to first state that I have no problem with the developer edition of ACF being limited. However, I find that the way it goes about it is anachronistic. It just grabs the first two non-127.0.0.1 IPs and adds them to the list of allowed IPs.
In the olden days (CF 6 and 7 let's say) that was fine. But, today, see how I have to develop:
I do my development on a Mac.
I have four virtual machines running Windows on two local Macs. Native IE6, Native IE7, Native IE8, and Native IE9. We do work for a government contractor and have to test in native versions of IE and that means a VM for each. Even though all of these VMs are local to my environment and have local-network IPs (i.e., 10.0.x.x), I can't use all of them to test locally. Only 2.
My suggestion: Change the licensing restrictions such that the following IPs will always let you test your ACF server locally:
127.0.0.1
192.168.x.x
10.0.x.x
Basically, if it's a browser requesting access from the local environment/system, let us have access to ACF.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3327214
External Customer Info:
External Company:
External Customer Name: craigkaminsky
External Customer Email:
External Test Config: My Hardware and Environment details:
Mac - iMac 9,1 (2009) 3.06 GHz, 8 GB RAM
Windows: 4 VMs (one on VMWare Fusion and three on VirtualBox)Attachments:
Comments: