I've included as much information as possible. I am completely confounded with this issue.. Microsoft wants a couple hundred dollars for a support incident to help me with it.
I have five main pages.
A) frontend.htm -- order entry front end, uses remote scripting and jscript [sets order_no cookie using jscript]
B) prodlist.asp -- list of configurable products
C) formX.htm -- actual product configuration page (jscript)
D) process.asp -- takes configuration information from formX.htm and adds it to the order [uses order_no cookie]
E) backend.asp -- backend asp for frontend.htm, uses order_no cookie
OK, that said, frontend.htm either creates a new order, or retrieves an existing order, and stores the order number in a cookie called order_no.
The user opens the prodlist.asp page and selects a product to configure. Which simply redirects to the appropriate formX.htm file (form[item_id].htm). These are Javascript based configurator pages that are compiled by another .asp file.
When they submit that form, process.asp runs and adds the configured items to the appropriate order number based on the order_no cookie.
I've colored the above section red, because this is where I have the problem. The cookie works on the prodlist.asp page (request.cookies("order_no"
) returns the order number. If I force the server to execute .htm files as ASP, then the cookie works on the formX.htm page as well with both request.cookies and javascript.. On the process.asp page the cookie doesn't work but only in IE 5.5 SP1, thats right it works in 5.5 and 5.0 but not 5.5 SP1.
I can't for the life of me figure out why.. I'm completely confounded. The cookie doesn't work in javascript OR request.cookies..
If anyone has any suggestions, I would love to hear them..
The workaround I've been using, is making formX.htm execute as ASP, and including a hidden field that contains the order_number. That works but it doesn't solve my underlying problem and it adds needless load to the web server..
The other place I have this cookie problem is in backend.asp
If I put cookie retrieval code in the description object (ie, request.cookies in the javascript code) it works fine. If I request cookies in the vbScript code that is called by the Javascript code, they don't work, once again only on IE 5.5
I can't find a solution.. I hope someone else out there knows of some workaround for IE5.5 SP1 that fixes this cookie issue, which as far as I can tell is a bug that was introduced in SP1.
I have five main pages.
A) frontend.htm -- order entry front end, uses remote scripting and jscript [sets order_no cookie using jscript]
B) prodlist.asp -- list of configurable products
C) formX.htm -- actual product configuration page (jscript)
D) process.asp -- takes configuration information from formX.htm and adds it to the order [uses order_no cookie]
E) backend.asp -- backend asp for frontend.htm, uses order_no cookie
OK, that said, frontend.htm either creates a new order, or retrieves an existing order, and stores the order number in a cookie called order_no.
The user opens the prodlist.asp page and selects a product to configure. Which simply redirects to the appropriate formX.htm file (form[item_id].htm). These are Javascript based configurator pages that are compiled by another .asp file.
When they submit that form, process.asp runs and adds the configured items to the appropriate order number based on the order_no cookie.
I've colored the above section red, because this is where I have the problem. The cookie works on the prodlist.asp page (request.cookies("order_no"
) returns the order number. If I force the server to execute .htm files as ASP, then the cookie works on the formX.htm page as well with both request.cookies and javascript.. On the process.asp page the cookie doesn't work but only in IE 5.5 SP1, thats right it works in 5.5 and 5.0 but not 5.5 SP1. I can't for the life of me figure out why.. I'm completely confounded. The cookie doesn't work in javascript OR request.cookies..
If anyone has any suggestions, I would love to hear them..
The workaround I've been using, is making formX.htm execute as ASP, and including a hidden field that contains the order_number. That works but it doesn't solve my underlying problem and it adds needless load to the web server..
The other place I have this cookie problem is in backend.asp
If I put cookie retrieval code in the description object (ie, request.cookies in the javascript code) it works fine. If I request cookies in the vbScript code that is called by the Javascript code, they don't work, once again only on IE 5.5
I can't find a solution.. I hope someone else out there knows of some workaround for IE5.5 SP1 that fixes this cookie issue, which as far as I can tell is a bug that was introduced in SP1.