I was helping Jason with this a bit before he posted here, but didnt have time
to do full tests.
I have run into this situation before and that time it automagically started
working the next day with an unaltered keystore. Arg!
So this issue:
I have a Win 7 VM with CF8.0.1 fully patched
How dangerous is increasing PostParameterLimit in CFv9 ? We have increased
from the default 100 to 1,100 to meet applications' needs. We are now
requested to consider increasing it to 2,000. The developers are reviewing
updating the design to use fewer PostParameters.
I don't have a good feel
Chris,
I believe the danger involves the risk of the HashDOS issues that Pete
elaborates on in his posts (which you cited). Is your application
public-facing or intranet-only (behind a corporate firewall)? If public
facing, then you have to weigh the potential for HashDOS vulnerability
Hi Guys,
I have been banging my head against a brick wall on something for a couple of
days now.
We have two load balanced Windows 2008 server running CF MX 7 on JRUN.
I am calling a simple HTTP API using CFHTTP. If I dump the XML which I get from
the response immediately after on one server
I am calling a simple HTTP API using CFHTTP. If I dump the XML which I get
from the response immediately
after on one server the output is ok, but on the other the unicode characters
are getting mangled.
i.e. médico becomes médico
I have called the API from a brand new IIS application
Are they both running off of the same database server? If not are all the
database table encodings set to UTF8? I had a similar Problem with a pair of
clustered PostgreSQL servers once where the second server defaulted to LATIN1
and was returning data like what you have below.
HTH,
Jon
On
Hi Dave,
I've done both of those things. My CFHTTP request has the charset=utf-8
parameter on it btw. On the rogue box when saving the cfhttp output to a
file it is still mangled. There is also a json response option from the API
and that too does the same to the data.
This the cfhttp header
Hi,
I have CF 9.0.1 installed, and I'm not able to define a Solr collection.
I get this error in the Administrator:
An error occurred while creating the collection:
org.apache.solr.common.SolrException. Check the Solr logs for more detail.
And in the Solr log, I get this:
JNDI not configured
might be a problem with the port being used, do you have anything else
running, other CF versions, other instances or anything like that ?
On Fri, Jan 17, 2014 at 9:18 PM, wrote:
Hi,
I have CF 9.0.1 installed, and I'm not able to define a Solr collection.
I get this error in the
might be a problem with the port being used, do you have anything else
running, other CF versions, other instances or anything like that ?
Nope. Nothing like that.
I noticed in solrConfig.xml something like
maxMergeDocs2147483647/maxMergeDocs
I thought It could be a too big number to read for a
10 matches
Mail list logo