LCCS Recording causes 404 error with HTTP HEAD

Avatar

Avatar

renatoferreirar

Avatar

renatoferreirar

renatoferreirar

28-07-2011

Hello everbody!

I'm trying to proceed with session recording, but I'm not receiving the file. I'm getting the following error instead:

access_log:

209.34.68.17 - - [28/Jul/2011:12:38:41 -0300] "HEAD /lccs-dav/na2%2Dsdk%2De72fda66%2Df06e%2D4702%2Db0b2%2D7c0c9aa51e35%5Fx002F%5Faudiocast%5Fx002F%5Ftime2011628124236510%2Ezip HTTP/1.1" 404 -

error_log:

[Thu Jul 28 12:38:41 2011] [error] [client 209.34.68.17] File does not exist: /mnt/disk2/lccs-recordings/na2-sdk-e72fda66-f06e-4702-b0b2-7c0c9aa51e35_x002F_audiocast_x002F_time2011628124236510.zip

Any suggestions?

Thanks,

Renato A. Ferreira

View Entire Topic

Avatar

Avatar

nzezelj

Avatar

nzezelj

nzezelj

01-08-2011

Sure, I didn't mean to imply that 404 and 401 errors are the same issue.  Only that if we somehow "converted" a 404 into a 401, things had a chance of working more smoothly.

Back to the issue, now that you also enabled the authentication for GET (and HEAD) do things work as "advertised" with authentication enabled?  That is, a plain HEAD is responded to with 401, and a subsequent PUT comes with proper credentials and succeeds?

I need to look at the authentication disabled workflow again.

Thanks,

Nikola