Spun up a VM Server using ol-server-7.2-x86_64-dvd.iso
Selected Software: Server with GUI, FTP Server, Java Platform, Network File System Client, Performance Tools, Print Server, Compatibilities Libraries, Development Tools

Verified public-yum-ol7.repo had correctly enabled latest, UEKR3, optional, and addons
yum update (Was successful)
vi /etc/selinux/config
Selinux=disabled
systemctl stop firewalld
systemctl disable firewalld
systemctl start sshd.service
systemctl enable sshd.service

At this point, the OL7 server was installed successfully and no errors in messages, etc...

Directly from the Foreman 1.10 Quick Start guide:

rpm -Uvh http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
rpm -ivh http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm
yum -y install epel-release http://yum.theforeman.org/releases/latest/el7/x86_64/foreman-release.rpm
yum -y install foreman-installer
yum clean all
vi each repo and enable SRMS and all other relevant stuff
yum repolist
yum update
foreman-installer
puppet agent --test

No Errors in foreman/puppet logs.

At this point, Foreman is successfully up and running. I am able to login and navigate through Foreman without any issues.

However, anytime I bring up an EXISTING object or create a NEW object, (ie.. create new domain, or smart proxy, etc) and click the Submit button, I get the following error:

"We're sorry, but something went wrong. We've been notified about this issue and we'll take a look at it shortly."

Within /var/log/foreman/production.log, the only error shown is the following: | Started GET "/domains" for 10.17.100.130 at 2016-02-03 10:38:13 -0600
2016-02-03 10:38:13 [app] [F] | EOFError (bad content body): | lib/middleware/catch_json_parse_errors.rb:9:in `call'

I repeated this exact same installation process using ver. Foreman Installer 1.9, I don't get the errors.

Again, the issue appears to be across the board every time I click the Submit Button in 1.10.

Enabling Debug mode doesn't show any more detail in regard to the error.

Any help would be appreciated.

UPDATE:
I tested Foreman 1.10 using IE 10 and Chrome 48.
The error above only happens in IE. This same process works using Chrome.
Something about IE ver 10.0.9/11x and Foreman 1.10 foreman-installer is not playing well together.