$_FILES["datei"]["size"] “

Datei:

To move the file to an upload folder, I created the folowing script (upload.php):

But after all, where is no file within the ipad/upload folder and I don´t know, what I´m doing wrong.

My target is to run a local instance of runalyze, withc can bei downloaded at www. Runalyze.de

<form action="url" method="post" enctype="multipart/form-data">
   <input name="name" type="file">
   <input value="Upload" type="submit">
</form>

iCab also supports many of the more advanced JS tricks to make upload forms more comfortable to use (like for example on the Facebook page). But there are a few things which do not work because of limitations of the iOS (like the “File reader” API), so this should be avoided in your own HTML code when the form should work on the iOS platform as well.

- For multiple file download, after I select 2 files, if I want to select 3rd file, it is not openning the “Downloads” folder to select my own file, rather it is only openning the default photo library
– Even after 2 file selected, if I do submit, after submit, I can only get download link for the 1st file from the server, which means only 1st of the 2 files selected got uploaded successfully

Is this a known behavior? Can you please throw some light on this?

Basically the implementation of your own HTTP protocol handler is a global thing to your App, so it is completely independent of UIWebView. UIWebView will internally load all the data from the internet using the standard networking routines of Cocoa and all these are using NSURLProtocol to find and process the networking stuff. So you do not need to do anything within the UIWebView delegates or methods. Just install your own HTTP protocol handler and it will be automatically called.

I’ll probably write a blog post about this topic soon. This is a little bit to big for the comments.

Your own protocol handler will be asked for all requests that are done via NSURLConnection if it will process this request. If it answers NO, then the standard handler will take over. You can even use NSURLConnections within your own handler to process the requests, but in this case your handler will be asked if it can process your own internal request as well, and to prevent a recursion you need to return NO here. Your internal requests needs to be processed by the standard HTTP protocol handler, but this is fine, because within your protocol handler you are able to modify or change the original request before sending it to the internet via your new internal NSURLConnection.

Using NSURLConnection within your protocol handler has the big advantage, that for almost all of the “callback” methods of the NSURLProtocol class there’s a corresponding delegate of the NSURLConnection class. So most of the delegate methods of NSURLConnection just look similar to this one (the parameters of the delegate method are passed to the protocol handler object):

- (void)connection:(NSURLConnection *)connection didReceiveData:(NSData *)data
{
	[[self client] URLProtocol:self didLoadData:data];
}

The only methods where you really need to do something more would be

- (void)startLoading

where you actually create a new connection for your (modified) request , and

- (void)stopLoading 

where you need to stop the connection, and

+ (BOOL)canInitWithRequest:(NSURLRequest *)request

Where you have to decide if you want to take over this request (in case it’s your form you need to modify), or if the standard handler needs to process it (it’s another request or its one of your internal requests where you’ve already modified the original requests).

According to your code: you should avoid using synchronous connections. Using the NSURLProtocol these are not needed.