Multidmedia Limited (MDM)
Search
advanced search »    
Quick Links
advanced search »
   Tuesday September 7th 2010

 




Untitled Document
+
Products & Solutions
 
Products
- Zinc 3.0 Builder
- Zinc 3.0 Plug-In Windows
- Zinc 3.0 Plug-In Mac OSX
- Zinc 3.0 Plug-In Linux
- Zinc 3.0 Development Suite
- Inferno 1.0 Windows
- Inferno 1.0 Mac OSX
Solutions
- Developers
- Designers
- Education
   
+
Support & Resources
 
Support
- Support Home
- Technotes & Known Issues
- FAQs
- Contact Us
Resources
- Software Updates
- Software Release Notes
- Software Bug Management
- Developer Articles
- File Exchange
- LiveDocs
- Support Forums
   
+
Purchase Online
 
- Online Shop
- Find a Reseller
- Volume Licensing
   
+
Company
 
- About Multidmedia (MDM)
- Client Showcase
- Legal Information
- Job Opportunities
- Press Room
- Blog
   
 

breadcrumbs

Home > Support > Bugs

 

Software Bug Management & Tracking

The MDM Software Bug Management and Tracking System is used to track and monitor the progress of user reported software bugs. You can search for a reported issue below to track it's progress and/or to get more information on an outstanding technical issue.


Bug Report #ZNC-9389RI
Verified on 18 September 2009
mdm.HTTP object handles 404 Error differently depending on server configuration  
Reported By Staff Member
This issue is Pending and is marked as a Medium priority.
 
Zinc 3.0 > Windows > Wrapper/Projector > 3.0.15 > Incorrectly Functioning  
Description
On some server configurations (where the error page is configured on the server but sull returns a HTTP 404 status code to the client) the 'onError' event is not fired. Instead, the content of the Custom Error page is downloaded to a local file.

Example:

//
var EXAMPLE_URL:String = "http://www.iarcmedia.com/invalid/invalid.jpg";
var myHTTP = null;
///
function initApp():Void
{
myHTTP = new mdm.HTTP();
myHTTP.onError = function():Void
{
mdm.Dialogs.prompt("Error occured");
};
//
myHTTP.onBinaryTransferComplete = function(obj:Object):Void
{
mdm.Dialogs.prompt(obj.filename);
};
//
var localPath:String = mdm.Application.path+"local_file.jpg";
myHTTP.getFile(EXAMPLE_URL, "", "", localPath);
}
//
setTimeout(initApp, 500);


The correct and expected behavior can be replicated in the following ActionScript 3.0 example:

//
var loader:URLLoader = new URLLoader();
loader.dataFormat = URLLoaderDataFormat.BINARY;
loader.addEventListener(HTTPStatusEvent.HTTP_STATUS, function(e:HTTPStatusEvent):void
{
trace("response status: "+e.status);
});
loader.addEventListener(IOErrorEvent.IO_ERROR, function(ioError:IOErrorEvent):void
{/* empty */});
var request:URLRequest = new URLRequest("http://www.iarcmedia.com/invalid/invalid.jpg");
loader.load(request);


The above code correctly reports the HTTP error status (and fires IOErrorEvent).
Attached File(s)
Click Here to download the Attached File
Resolution
Pending

View all Pending Bug Reports » Report a new Software Bug/Issue »

 

 
Multidmedia Limited (MDM)

AddThis Social Bookmark Button
Copyright © 2002-2010 Multidmedia Limited (MDM) All rights reserved. Use of this website signifies your agreement to the Terms of Use.
Flash, Flex and associated Logos are the Registered Trademarks of Adobe Systems, Inc.
There are currently 34 Users Online.