Hi
Is there a way that we can display the friendly url of the file path to documents. We are just setting up the log reporting in webtrends and need to be able to report on file uploads for the different area's in our organisation.
At the moment the logs are generated and only show /__data/assets/file type/asset no/file name
we have our document area set up with subdirectories of the various sections so for instance we need to report on all files and subdirectories of these areas.
This is how we can view them before the asset is live, which is great but how do we log (apache) this friendly url??? without it reverting to /__data/etc
eg. when I run the report for "section", it should show me all page access (it does) and all document downloads under the "section" directory. All we can get out is the /__data/ stuff and this is for every document under the documents directory. All we need in this example is the "section" sub directory???
Has anyone had this issue or can provide some assistance??
Regards
Andrew
The only way to revert back to the Friendy URL is to disable the "Allow Unrestricted" option on the details screen of the file. Otherwise, once the file goes live, its URL actually changes to the Unrestricted URL which is what you're seeing in the log file.
However, you have to do this manually for each file.
Hi Avi
Thanks for that.
Have tried on a couple of doc's and checked the logs and they are showing the full path now.
It seems a bit strange that this option is set to yes by default when the permissions on the files are public any way?? ie they are getting served up any way. What is the reason for this to happen???
What do you percieve as being any issues with setting these to no and is there not a script or hippo that can be run to change the status on more than one? It will be quite a big task doing each separately and getting any one that uploads a new file to set it to no.
Andrew
The reason is performance: The Unrestricted URL files are served directly by Apache and are preferred from a performance point-of-view. If you disable Allow Unrestricted, it means Matrix has to serve all the files which is significantly slower.
Remember, you created an alias for the /__data location in Apache. When a file is Live with Public Read, Matrix copies it into this location, so that Apache can serve it.
You would need to determine what is more important: Simplified analysis from the URL in the logfile vs. the negative impact to performance by having Matrix serving all the files. Though, you may not see that impact unless your site has medium to heavy traffic.
At present there is no way to mass change this setting. You would have to submit a feature request or even fund the development for this.
Edited to add that I do not recommend changing this for all files. Rather, I would strongly recommend changing your logging/analysis so that you can link particular files to their new data URL.
Would this also cause issues with the 'Page at a time' or 'Bysteserving' of PDF's if matrix has to push out the files, rather than directly from apache? If its coming direct from apache then it can 'stream' the delivery of the pdf to support this feature, but if php has to stream this, isn't it alot harder? or does not acheive the same thing?
[quote]Would this also cause issues with the ‘Page at a time’ or ‘Bysteserving’ of PDF’s if matrix has to push out the files, rather than directly from apache?
[right][post=“12053”]<{POST_SNAPBACK}>[/post][/right][/quote]
Correct. Matrix will have to deliver the entire file – Acrobat’s plug-in will probably not be able to stream pages.
[quote]Correct. Matrix will have to deliver the entire file – Acrobat’s plug-in will probably not be able to stream pages.
[right][post=“12054”]<{POST_SNAPBACK}>[/post][/right][/quote]
Thats what I was thinking. That feature is great for PDF’d that have been web optimised, and over about 500k I think it is… it allows first page to download, then subsequent pages load in the background…
True.
I do need to stress the performance impact of disabling Unrestricted Access: It means that Matrix has to be fired up and needs to deliver the file. This is significantly slower than Apache delivering the file directly.