There are no settings in Witango that will correct your issue. You must truncate the cookie length on the sending server.
I believe this issue was corrected in TeraScript 6.2.7. I just did a quick test in TeraScript 7.1.1 and it worked correctly. The maximum length for a cookie is 3071 bytes. A longer cookie will be silently truncated and the query will continue to process normally. Robert From: [email protected] [mailto:[email protected]] Sent: Tuesday, August 09, 2016 12:31 AM To: [email protected] Subject: Re: TeraScript-Talk: Problem on Listening Terascript port Hi, Currently SessionID and SessionEntitiy cookies having more than 1000 characters. When we reduced manually by passing the cookie as 250 characters each then it reaches OLE server and we could able to see the log. Is there any configuration in witango to accept the cookies more than 1000/2000 characters ? Thanks & Regards Prabakaran _____ From: Robert Shubert <[email protected] <mailto:[email protected]> > Sent: Monday, August 8, 2016 11:56:29 PM To: [email protected] <mailto:[email protected]> Subject: RE: TeraScript-Talk: Problem on Listening Terascript port Then I suspect that the request is being corrupted as it moves from the plugin to the server. Your only option will be to determine which header is causing the problem and adjust it (remove special characters, shorten the length, etc) From: [email protected] <mailto:[email protected]> [mailto:[email protected]] Sent: Monday, August 08, 2016 4:44 AM To: [email protected] <mailto:[email protected]> Subject: Re: TeraScript-Talk: Problem on Listening Terascript port There is no entry in Witango for this failure transaction even START entry also Thanks & Regards Prabakaran ITIL - V3 Certified BSS Type II & III, Project Primus (Optus) Accenture, Chennai, India EXTN: +61 2895 63178 |MOBILE: +91 8056810457 _____ From: Robert Shubert <[email protected] <mailto:[email protected]> > Sent: Friday, August 5, 2016 10:11:26 PM To: [email protected] <mailto:[email protected]> Subject: RE: TeraScript-Talk: Problem on Listening Terascript port Output information about the request at the top of the TAF, such as writing to a file or sending an email. You should also see a START entry in the witango.log From: [email protected] <mailto:[email protected]> [mailto:[email protected]] Sent: Friday, August 05, 2016 8:57 AM To: [email protected] <mailto:[email protected]> Subject: Re: TeraScript-Talk: Problem on Listening Terascript port Hi Robert, Those cookies are necessary to run the application. Is there any other way to check whether the transactions weather it reaches witango or not? Thanks & Regards Prabakaran _____ From: Robert Shubert <[email protected] <mailto:[email protected]> > Sent: Friday, August 5, 2016 9:19:00 PM To: [email protected] <mailto:[email protected]> Subject: RE: TeraScript-Talk: Problem on Listening Terascript port It sounds like a corruption in the communication between Apache and Witango. Since it seems to occur when a certain cookie is present, I would narrow it down to that cookie, perhaps you can configure the IDP to not send that cookie. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] Sent: Friday, August 05, 2016 8:39 AM To: [email protected] <mailto:[email protected]> Subject: Re: TeraScript-Talk: Problem on Listening Terascript port Hi Robert, There is no entries in witangoevents.log and witango.log file for this transaction, even logging level configured as "3". Also we have noticed that whenever the browser throws proxy error that time in cookie we could able to see the WitangoUserReference value. Is that mean it reaches witango server and getting error due to some reason but log not captured anywhere? Is there any way to troubleshoot this issue? Thanks & Regards Prabakaran _____ From: Robert Shubert <[email protected] <mailto:[email protected]> > Sent: Friday, August 5, 2016 8:36:20 PM To: [email protected] <mailto:[email protected]> Subject: RE: TeraScript-Talk: Problem on Listening Terascript port Check witangoevents.log to see if the Witango server is crashing. Some cookie values can cause the server to crash. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] Sent: Friday, August 05, 2016 7:46 AM To: [email protected] <mailto:[email protected]> Subject: TeraScript-Talk: Problem on Listening Terascript port Hi, We are using Witango 5.5 Server in our application. Recently we have implemented Single sign on concept in our application. once we hit the URL of our application it redirects to IDP (identity provider) and will display the login page. After user get authenticated it will come to our application via POST method. Currently when it redirects to IDP to our application it throws 500 -Proxy ERROR in browser. When we check the Apache web server log its hanging on listening on port 80 (witango port) and in witango log we cannot able to see the request at all. But we have created on sample HTML file and called our application with same POST argument and it reaches successfully to Witango. The difference between two POST is, in original transaction some browser cookies are coming from IDP to our application. But in our sample HTML file there is no cookie. Will Witango server behave differently based on Cookie value? is there any configuration change I need to check? Can someone help me why Witango port itself not listening for this particular transaction. Thanks & Regards Prabakaran _____ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com <http://www.accenture.com> _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe terascript-talk" in the body.
