Lighttpd

I have tried the patch. I am no longer getting the error I was. The upload is happening, but I cannot get the status. At this point, I'm not sure whether the problem is mine or yours. If you could give me a little guidance, I'll keep trying.

My config file contains:

upload-progress.progress-url = "/uploadprogress"
upload-progress.debug = "enable"

The upload url is:

<form action="/migration/upload?X-Progress-ID=12345678901234567890123456789012" name="form" method="post" enctype="multipart/form-data">

although the parameter is gone when it gets logged (not surprising).

The status url is logged as:

10.100.1.126 hyperion.intradyn.com - [08/May/2017:21:57:15 +0000] "GET /uploadprogress?X-Progress-ID=12345678901234567890123456789012 HTTP/1.1" 302 0 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0"

and the I'm being told it's an invalid url (again, not surprising, as I haven't defined that url).

My understanding is that the httpd server itself should answer the request, and my code should never know it happened. The upload is completing successfully, but I cannot get status. Please let me know if you see an error in my setup.

Oh, and my defined modules are:

server.modules = (
"mod_uploadprogress",
"mod_expire",
"mod_rewrite",
"mod_alias",
"mod_access",
"mod_fastcgi",
"mod_accesslog",
"mod_magnet"
)

You haven't provided your entire config and the mistake is probably there. lighttpd -f /etc/lighttpd/lighttpd.conf -p

10.100.1.126 hyperion.intradyn.com - [08/May/2017:21:57:15 +0000] "GET /uploadprogress?X-Progress-ID=12345678901234567890123456789012 HTTP/1.1" 302 0 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0"

Why is lighttpd returning a 302 for that page? Do you have mod_expire add caching headers to all requests? (Don't do that.)

What headers does your browser send with the GET request? Either use the tools available in your browser, or set debug.log-request-header = "enable" in lighttpd.conf and look at the error.log after making the GET request.

In our product, any URL not recognized returns a redirect to a default page with an error set. My understanding is that the back-end should never see this request if it is recognized as a upload status request.

It would appear that your product is responding to GET /uploadprogress?X-Progress-ID=12345678901234567890123456789012 You should verify that since mod_progress should not be responding with a 302 redirect. Look in the lighttpd access.log (mod_accesslog is enabled) or set debug.log-request-header = "enable" in lighttpd.conf and look at the error.log after making the GET request.

If the request is reaching lighttpd, then this rule in your config might intercept the request before mod_uploadprogress gets a chance

    url.rewrite-once               = (
        "^/media/(.*)"      => "/media/$1",
        "^/vault/tmp/(.*)$" => "/vault/tmp/$1",
        "^(/down/.*)$"      => "/down.fcgi$1",
        "^(/.*)$"           => "/cv4.fcgi$1",
    )

That's it. By adding a new rewrite rule:

"^/uploadprogress(.*)$" => "/uploadprogress$1",

I can now get the progress information.

Thank you very much for your help.