Why have you added the "\\1" at the end?
These side of the filter parameter is a path in your filesystem... Have you a directory called "\\1"?
If you whis only read jpg files the way to do is some like this:
ModPagespeedLoadFromFileRuleMatch disallow .* (this disallow any file)
ModPagespeedLoadFromFileRuleMatch allow \.(js|css|jpg|jpeg|png|pdf|gif)(\?.*)?$ (this allow only files with these extensions)
The order matter. If you don´t use the disallow directive and only use the allow, any other file can be loaded, because no disallow is presente.
If you put the disallow in the last position, no files are allowed
About these other filters:
When you load a file from the filesystem, no http request is made, so no http headers are in place then tread the loaded files as it have a cache-control: max-age=
And the other is tread any resource fetched by http request that don´t have a cache-control header put one with a max-age of
I think is not a good idea put 1 year here. Why? These resources are stored in the pagespeed cache for 1 year, The resource loaded from filesystem is renewed each time the file changes, same the resource fethed by http, if the hash changes the optimized resource is renewed, but maybe the old resources still in the pagespeed cache until it expires or is evicted to make space for new items, so a sort time is better.
These times must be a deal between space in the pagespeed cache and how much times the resource need to be renewed.
These 2 parameters are NOT the time in what the resource is stored in the browser cache, a optimized resorce have a ttl for the brownser for 1 year..
You see it in a
ModPagespeedLoadFromFileMatch filter. This filter permit regular expressions,
ModPagespeedLoadFromFile NOT. And \\1 is part of a regular expression.