Saving Template changes-Bad Request Error

[bullergotya]

When I click the Save changes button I get a bad request error page, this worked before upgrading to 1.8.1. Diagnostics runs fine says everything is OK, when I first logged in it updated to 1.8.1, all the paths are correct and chmods are correct. Anyone have any ideas why I get the Bad Request Error?
Update: Tried posting and that works perfectly and also Rebuild everything, it all works fine just the Save changes for the Templates. Checked the Error file on the server but nothing shown about that error.

[petefinnigan]

Hi,

I justed tested the same on my 1.8.1 test blog and it saved fine. Eactly what template did you change, what did you change and can you screen ptint the error - if you can repeat the error?

cheers

Pete

[bullergotya]

Hi Pete
Added a link to the main index page on the main archives template, clicked the save button and was taken to the Bad Request error page. Tried no changes on any templates it still went to the Bad Request Error page:
Bad Request
Your browser sent a request that this server could not understand.
Make sure the link is typed correctly.
Client sent malformed Host header.

[coldstone]

There is a slight difference now in how the templates are saved. Previously, when you selected a template section to edit, all the templates you weren't editing would be encoded as hidden fields on the page. With 1.8.1 you are editing all the templates, so there is no encoding.

I wonder if there is a template that you hadn't edited, or edited long ago that your webserver doesn't like. If you want, you could try making a copy of your gm-templates.cgi file (save it somewhere safe).

• delete all your templates and try saving to see if that works.
  
• restore templates from your backup by coping your backup file to gm-templates.cgi
  
• if that worked, you could then try deleting your templates one-by-one to see if there is a particular template that is causing this error.
  

[bullergotya]

Removed temps from cgi file and clicked Save:

The templates have been modified. Be sure to rebuild your files to make these changes take effect throughout your site.

So it must be a temp, well have my work cut out for me, lol


I will try that coldstone and post back, Thank You

[coldstone]

No problem, I know its tedious work, I have done it a couple times.

One thing that might make it go faster is if you do large sections, then when you find the general area, concentrate on that area.

[petefinnigan]

Hi Guys,

Does the request send the whole (of the templates) in one go or in steps?, I am not sure without looking. If its sent in steps then you could install ethereal (or wireshark as its now known) and capture the request that fails, it may help you hone in on the issue.

A second idea would be to pass the template through an HTML validator and see if that gives you some clues on what is wrong.

cheers

Pete

[coldstone]

It sends the all the templates, which is the same as pre-1.8.1, its just pre-1.8.1 it used html hidden inputs to store all the templates not being edited. Those hidden fields were 'encoded' by Greymatter (such as changing certain characters to others).

[petefinnigan]

Thanks for the clarification Coldstone, I guess my suggestion to run the template through a validator may still work though?

[coldstone]

Maybe, I am not sure. The resulting page still should be valid, but it might not hurt to check. I just haven't seen that error from a badly formated web form or page. I am suspicious that its another ISP that is filtering the incoming traffic for certain keywords. Its a different error, but so far feels similar to the 'Forbidden' issue previous people ran into.

[petefinnigan]

you could be right, this does sound like that issue.

cheers

Pete

[bullergotya]

Figured out what is was. I tried having my java script menu on my blog, but would never show, once I removed that code from my main index page I was able to save my template changes.

[coldstone]

Yeah, I saw a site like that. It would give a 500 error whenever a user tried to upload any template with '>script' in it . If Greymatter catches something like that, it will give you an error screen that it doesn't take kindly to that kind of behavior.

You might be able to include a seperate js file with a meta tag on your page. If you are paying this webhost though, I would bring it up with them.

[petefinnigan]

Hi Coldstone,

I am not convinced.

It may be that direct java script embedded in a template causes an issue but having a script tag doesn't also cause an issue. I have a number of included javascript files on my site for my menus, see the URL below in my signature for my oracle security site blog. But to include them i need to use the script tag in the header template and also in a custom template. So whilst i can agree that javascript directly embedded may cause an issue, and also agree that adding any java script via an included file is fine (at least for me) i am not convinced about the use of script tags causing a 500 error in all cases if included in a template as i have obviously done that.

cheers

Pete

[bullergotya]

It was not <script></script> in the <head> it was
( <div align="center"><table border=0 cellpadding=0 cellspacing=0><tr><td><script language="javascript" src="sftmp1arrays.js"></script><script language="javascript">var HOPBn=false;uagent = window.navigator.userAgent.toLowerCase();HOPBn=(uagent.indexOf('opera') != -1)?true:false;var IEC=false;var scompat = document.compatMode;if(scompat != "BackCompat"){IEC=true;}else{IEC=false;}if((document.all)&&(HOPBn==false)&&(IEC==false)){document.write('<div id="tmp1hmplcmenu1" style="position:relative;width:622px;height:24px;background:#AEDFFF;padding:0px;overflow:hidden;border-width:0px;"></div>'); document.write("<scr"+"ipt language=\"javascript\" sr"+"c=\"sfmenutmp1ie.js\"></scr"+"ipt>");}else{ document.write("<scr"+"ipt language=\"javascript\" sr"+"c=\"sfmenutmp1ns.js\"></scr"+"ipt>");}</script></td></tr></table></div><br>)
this in the <body></body> once I removed it everything was fine, it is the code for my menu.