Skip to main content
R
richardELeach
Inspiring
July 28, 2014
Answered

CF11 cflocation BAD REQUEST

  • July 28, 2014
  • 2 replies
  • 2549 views

Hi

What was working fine in CF8:

<cflocation url="index.cfm?action=receivable.actRetrieveJobReceivablesEdit&jobId=#viewstate.getValue('jobid')#&estimateId=#viewstate.getValue('estimateId')#" statuscode="302">

Now breaks in CF11, I get an error "Bad Request" and then the CSS styles get dumped onto the user's screen.

I read up on the security enhancements to CF11 and noticed the addToken attribute's default had been changed, so I added "addToken=true" but the error persists.

Also, the web server is IIS7.5.

Has anyone else run into this?

Thanks,

Rich

This topic has been closed for replies.
Correct answer richardELeach

... actually after a closer inspection of the log files the problem was solved by increasing the value in the Maximum number of POST request parameters which is in the Server Settings panel.

Thanks for all of your good ideas.

Rich

2 replies

BKBK
Community Expert
BKBKCommunity Expert
Community Expert
July 28, 2014

The automatic URL encoding is perhaps messing things up. Try composing the link outside the cflocation tag, as follows:

<cfset action="receivable.actRetrieveJobReceivablesEdit">

<cfset jobid=viewstate.getValue('jobid')>

<cfset estimateid=viewstate.getValue('estimateid')>

<cfset link = "test.cfm?action=#action#&jobId=#jobid#&estimateId=#estimateId#">

<cflocation url="#link#" statuscode="302">

R
richardELeachAuthorCorrect answer
Inspiring
July 28, 2014

... actually after a closer inspection of the log files the problem was solved by increasing the value in the Maximum number of POST request parameters which is in the Server Settings panel.

Thanks for all of your good ideas.

Rich

BKBK
Community Expert
BKBKCommunity Expert
Community Expert
July 28, 2014

Quite curious. Could you share what the logs say with us?

EddieLotter
EddieLotter
Inspiring
July 28, 2014

I don't use CF11, but some troubleshooting tips:

  • Try hard coding the URL of the cflocation tag and test it.
  • If it works then assign the URL you are constructing to a string and dump that string so that you can verify that it is the URL you expect it to be.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices