Re: Strange behavior from Apache with DirectAction String greater than 504 characters

On 08.09.2005, at 12:16, Andreas Hjortsberg wrote:

> Hello!
> As of Apples new strategy to only support there own plattform for  
> deployment of WO53,  we decided to try move from Windows to OSX.

Cool, Apple will be glad that this strategy worked for at least on  
customer (sorry, could not resist) ;-)

> So we  lended an XServe from a local retailer but we have had some  
> problems when it comes to long Direct Action strings.
>
> We did an standard installation of OSX server, Tiger. WO 5.2.4  and  
> Apache 1.3 was already installed, so the only thing we did was to  
> add our application and framworks,  added the needed  information  
> to the monitor and changed som rights in our files. So far  
> everything is just fine.
>
> We can acces our application on just fine on http://192.168.10.2/ 
> cgi-bin/WebObjects/XOdus.woa
> Now to the strange part. We have an external pure java client that  
> books transaction by creating direkt actions strings and  if on of  
> those is longer than 504 character the webserver won't respond. No  
> access attempts will be found in /var/log/httpd/access_log. If I  
> take that generated string and paste it into my browser and then  
> press enter I get  "Page can not be found" . But if I first access  
> the application on   http://192.168.10.2/cgi-bin/WebObjects/ 
> XOdus.woa and then paste  in the URL and press enter the  
> application will respond correctly and the access_log will have a  
> record of my attempt. And the transaction will be created in our  
> application.
>
> I'm quite confused. Is there some security settings that I'm not  
> aware about? Can I increase the logging in Apache?
> How can I check that everyting is configured correctly between the  
> adapter and Apache?
>
> This works just fine with IIS on Windows Server so I do hope it's  
> my lack of knowledge in the subject.
>
> I would realy keep the lended XServe but will have some problem to  
> convince my Manager to do so if we can't run our application on it.
>
> As Always any ideas is welcome
>

Strange things. But please do the following:

make sure your urls are not longer than 1024 characters 'cause this  
leads to problems. I would suggest to use POST instead of GET which  
has not this limitation. No real help, just a work around.

regards, David

> Regards
> /Andreas
>
>
> This one will go* *without any problems at all.
>
> http://192.168.10.2/cgi-bin/WebObjects/XOdus.woa/wa/createReceipt? 
> &created=20050908094306&creatorCashDesk=5001&creatorStation=IT9&creato 
> rEmployee=sad&fees=20.0&commissions=0.0&balanceReturned=-0.09&rows=2&1 
> _receiveContainer=5001&1_chargeContainer=892&1_item=5&1_measuredQuanti 
> ty=11.0&1_transactionType=B&1_transactionRate=7.5377&1_selectedRateDef 
> inition=3&2_receiveContainer=5001&2_chargeContainer=892&2_item=3&2_mea 
> suredQuantity=-63.0&2_transactionType=P&2_transactionRate=1.0&receiptC 
> omment=12345678+
>
>
> This wont
>
> http://192.168.10.2/cgi-bin/WebObjects/XOdus.woa/wa/createReceipt? 
> &created=20050908094343&creatorCashDesk=5001&creatorStation=IT9&creato 
> rEmployee=sad&fees=20.0&commissions=0.0&balanceReturned=-0.09&rows=2&1 
> _receiveContainer=5001&1_chargeContainer=892&1_item=5&1_measuredQuanti 
> ty=11.0&1_transactionType=B&1_transactionRate=7.5377&1_selectedRateDef 
> inition=3&2_receiveContainer=5001&2_chargeContainer=892&2_item=3&2_mea 
> suredQuantity=-63.0&2_transactionType=P&2_transactionRate=1.0&receiptC 
> omment=123456789+
>
>
>
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>