So, I’ve managed to get a domain on there that was not in use and had a valid SSL.
I ran the code that I attached above to create some cookies with UUID for values, and the same issue occurred
I then went to C:\lucee\tomcat\conf and edited the server.xml file, changing the following values from 16384 to 65536, and rebooted the server… it didn’t fix it
The only thing I might be missing is the BonCodeAJP13.settings file in the C:\windows folder, where @andreas had mentioned “Then change the AJP Boncode PacketSize in the Boncode Settings (see BonCode Apache Tomcat AJP 1.3 Connector)” however, I don’t see any reference to packsize in there.
Got it. PackSize added to the BON file. Rebooted (btw I have odd behaviour on 8888 if I just stop the service and restart it, I get a welcome to your lucee installation page, the root appears to change, only a reboot seems to fix it)
We’re getting somewhere with this. Using port 8888 it works! In the link @Julian_Halliwell provided above I also see that it maxes at 200 cookies by default so for my particular situation that might be something worth looking at.
The problem is that it won’t work outside of port 8888, it has the same issue, so I guess that somewhere else I need to amend to 65536 or perhaps add additional entries?
Try adding packetSize="65536" to the AJP connector definition in your Tomcat server.xml. It looks similar to the HTTP connector you modified before but with protocol="AJP/1.3", and probably on port 8009.
playing devils advocate here,
what exactly are you using IIS for with lucee?
If you’re not using any IIS specific application hooks, I would suggest ditching it, as apache (or nginx) are faster, more resource efficient and far less of a security risk that IIS.
How many cookies are you setting? The default maximum Tomcat allows via AJP is apparently 200. If you are setting more than that then perhaps increasing it via the maxCookieCount attribute in the AJP connector might help?
@Terry_Whitney understood, but I’m used to IIS and don’t want to change too much at once, maybe in the future, but I don’t want to go through the pain of using anything else right now. I am already juggling more than I’d like while working on a new project.
@Julian_Halliwell yes, I noticed that. The platform that I need to get working is 69 cookies, an odd one might sneak in along the way. The test I am doing is for 100 test cookies with the UUID value. I did notice that in the link of parameters that I could change from default
install application-request routing and url-rewrite, if you have not already
after you restart the service you can add a url rewirte
then you can add cfc/cfm/cfml as rewrites for your website
rewrite url: http://yourluceeinstall:8888/
I do have re-write installed already, I use it to rewrite if the user is not on the WWW. and also from HTTP to HTTPS.
Not sure how I’d use it to fix this problem, although I do know I don’t have this issue on ACF. The simple fix does appear to be a reboot, a little odd how a stop start causes this to change
Thanks for the lengthy instructions on the re-write although I’m not sure what it’s actually doing and therefore how it fixes the issue.
The issue is that the headers were too large due to the 69+ cookies, however as above I made various tweaks to the Lucee config files and it started working on port 8888 when I tested it locally on the server. However I’m struggling to understand how to increase the header size to 65535 for public ports so that the site works for everybody.
I thought it might be a good idea to summarize this
The issue is my headers are too large which is causing Lucee to throw the error. This is caused by me having to write at least 69 cookies (As above I realize it is set to max at 200 in the Lucee config)
BonCodeAJP13.settings in C:\Windows folder added the line <PacketSize>65536</PacketSize>
Once all of this was added I was able to get the site to work locally on port 8888, however, I am unable to get it to work beyond that, the same error/header restriction appears if I try to access it it publicly
You could try looking into the default header limits in IIS and try to increase them accordingly like you have done on BonCode and Tomcat. Maybe IIS is truncating them in some way???
I don’t believe it’s an IIS issue, I have the site running on an IIS server with no problem. I cloned the server, uninstalled CF and put lucee on the clone, so the IIS settings are the same, and work.