When uploading big file (>100M) to server, PHP always accept entire data POST from browser first. We cannot inject into the process of uploading.
For example, check the value of "token
" before entire data send to server is IMPOSSIBLE in my PHP code:
<form enctype="multipart/form-data" action="upload.php?token=XXXXXX" method="POST">
<input type="hidden" name="MAX_FILE_SIZE" value="3000000" />
Send this file: <input name="userfile" type="file" />
<input type="submit" value="Send File" />
</form>
So I've try to use mod_rewrite
like this:
RewriteEngine On
RewriteMap mymap prg:/tmp/map.php
RewriteCond %{QUERY_STRING} ^token=(.*)$ [NC]
RewriteRule ^/upload/fake.php$ ${mymap:%1} [L]
map.php
#!/usr/bin/php
<?php
define("REAL_TARGET", "/upload/real.php\n");
define("FORBIDDEN", "/upload/forbidden.html\n");
$handle = fopen ("php://stdin","r");
while($token = trim(fgets($handle))) {
file_put_contents("/tmp/map.log", $token."\n", FILE_APPEND);
if (check_token($token)) {
echo REAL_TARGET;
} else {
echo FORBIDDEN;
}
}
function check_token ($token) {//do your own security check
return substr($token,0,4) === 'alix';
}
But ... It fails again. mod_rewrite
looks working too late in this situation. Data still transfer entirely.
Then I tried Node.js
, like this (code snip):
var stream = new multipart.Stream(req);
stream.addListener('part', function(part) {
sys.print(req.uri.params.token+"\n");
if (req.uri.params.token != "xxxx") {//check token
res.sendHeader(200, {'Content-Type': 'text/plain'});
res.sendBody('Incorrect token!');
res.finish();
sys.puts("\n=> Block");
return false;
}
Result is ... fail again.
So please help me to find the correct path to resolve this issue or tell me there is no way.
Related questions:
Can PHP (with Apache or Nginx) check HTTP header before POST request finished?
Use javascript. Submit a pre-form via ajax when user clicks submit, wait for the ajax response, then when it comes back successful or not, submit the actual form. You can also have a fallback to the method you don't want which is better than nothing.
Why dont you just use the APC file upload progress and set the progress key as the key for the APC file upload so in that case the form is submitted and the upload progress will start initially but then at the first progress check you will verify the key and if its not correct you will interrupt everything:
http://www.johnboy.com/blog/a-useful-php-file-upload-progress-meter http://www.ultramegatech.com/2008/12/creating-upload-progress-bar-php/
This is a more native approach of doing it. Roughly the same, just change the key of the hidden input to your token and validate that and interrupt the connection in case of an error. Maybe thats even better. http://php.net/manual/en/session.upload-progress.php
First of all, you can try this code yourself using the GitHub repo I created for this. Just clone the repository and run
node header
.(Spoiler, if you're reading this and are under time pressure to get something to work and not in the mood to learn ( :( ), there is a simpler solution at the end)
The general idea
This is a great question. What you are asking for is very possible and no clientside is needed, just a deeper understanding of how the HTTP protocol works while showing how node.js rocks :)
This can be made easy if we go one level deeper to the underlying TCP protocol and process the HTTP requests ourselves for this specific case. Node.js lets you do this easily using the built in net module.
The HTTP Protocol
First, let's look at how HTTP requests work.
An HTTP request consists of a headers section in the general format of key:value pairs seperated by CRLF (
\r\n
). We know that the header section ended when we reach a double CRLF (that is\r\n\r\n
).A typical HTTP GET request might look something like this:
The top part before the 'empty line' is the headers section and the bottom part is the body of the request. Your request will look a bit differently in the body section since it is encoded with
multipart/form-data
but the header will remain similarLet's explore how this applies to us.TCP in nodejs
We can listen to the raw request in TCP and read the packets we get until we read that double crlf we talked about. Then we will check the short header section which we already have for whatever validation we need. After we do that, we can either end the request if validation did not pass (For example by simply ending the TCP connection), or pass it through. This allows us to not receive or read the request body, but just the headers which are much smaller.
One easy way to embed this into an already existing application is to proxy requests from it to the actual HTTP server for the specific use case.
Implementation details
This solution is as bare bones as it gets. It is just a suggestion.
Here is the work flow:
We require the
net
module in node.js which allows us to create tcp servers in node.jsCreate a TCP server using the
net
module which will listen to data:var tcpServer = net.createServer(function (socket) {...
. Don't forget to tell it to listen to the correct portsocket.on("data",function(data){
, which will trigger whenever a packet arrives.socket.end()
which will close the connection.Here are some things we'll use
A method for reading the headers:
A method for checking double CRLF in a buffer you get on a data event, and return its location if it exists in an object:
And this small utility method:
Implementation
If you have any questions feel free to ask :)
Ok, I lied, there is a simpler way!
But what's the fun in that? If you skipped here initially, you wouldn't learn how HTTP works :)
Node.js has a built in
http
module. Since requests are chunked by nature in node.js, especially long requests, you can implement the same thing without the more advanced understanding of the protocol.This time, let's use the
http
module to create an http serverThis is based on the fact the
request
handle in a nodejshttp
module actually hooks on after the headers were sent (but nothing else was performed) by default. (this in the server module , this in the parser module)User igorw suggested a somewhat cleaner solution using the
100 Continue
header assuming browsers you're targeting supports it. 100 Continue is a status code designed to do exactly what you're attempting to:Here it is :
You can see sample input/output here. This would require your request to fire with the appropriate
Expect:
header.One way to bypass PHP's post handling is to route the request through PHP-CLI. Create the following CGI script and try uploading a large file to it. The web server should respond by killing the connection. If it does, then it's just a matter of opening an internal socket connection and sending the data to the actual location--provided that conditions are met, of course.
Previous version was somewhat vague. So I've rewritten the code to show the difference between route handling and middleware. Middlewares are executed for every request. They are executed in the order they are given.
express.bodyParser()
is the middleware which handles file upload, which you should skip, for incorrect tokens.mymiddleware
simply checks for tokens and terminates invalid requests. This must be done beforeexpress.bodyParser()
is executed.uploadhandler
on the other hand cannot interrupt the upload as it has been processed byexpress.bodyParser()
already. It just processes the POST request. Hope this helps.I suggest you to use some client side plugins to upload files. You could use
http://www.plupload.com/
or
https://github.com/blueimp/jQuery-File-Upload/
Both plugins have provision to check file size before uploading.
If you want to use your own scripts, check this. This may help you