When you put up the popup, execution does not stop like it does in other
environments so the next lines of code might run and end up calling the
webservice.

 

________________________________

From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of markcavins
Sent: Thursday, January 10, 2008 10:27 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Massive Error for login script

 

Hello,

I am having a major problem with my login script. When a user enters
information correctly there is not problem. if a user enters in the
wrong customer name I get the expected popup that says enter your
customer #. However if the username or customer name is wrong the
browser pops up a warning (set by a serverside js warning used by
other programs) and I get the following error

[RPC Fault faultString="HTTP request error"
faultCode="Server.Error.Request" faultDetail="Error: [IOErrorEvent
type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error
#2032: Stream Error. URL:
https://mysite.net/interface.php?password=pass&customer=13&username=uzer
namz
<https://mysite.net/interface.php?password=pass&customer=13&username=uze
rnamz> "].
URL: https://mysite.net/interface.php <https://mysite.net/interface.php>
"]
at
mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faul
tHandler <http://www.adobe.com/2006/flex/mx/internal::faultHandler>
()[E:\dev\flex_3_beta2\sdk\frameworks\projects\rpc\src\mx\rpc\AbstractIn
voker.as:211]
at
mx.rpc::Responder/fault()[E:\dev\flex_3_beta2\sdk\frameworks\projects\rp
c\src\mx\rpc\Responder.as:56]
at
mx.rpc::AsyncRequest/fault()[E:\dev\flex_3_beta2\sdk\frameworks\projects
\rpc\src\mx\rpc\AsyncRequest.as:110]
at
DirectHTTPMessageResponder/errorHandler()[E:\dev\flex_3_beta2\sdk\framew
orks\projects\rpc\src\mx\messaging\channels\DirectHTTPChannel.as:343]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/redirectEvent()

I have read articals like judah's blog I am still stumped how to fix
this issue.

 

Reply via email to