Previous Next  Up  Table of Contents  EagleFiler Home

7.10   Why does EagleFiler import the wrong Web page when I press the capture key?

Some Web pages—such as order confirmations and credit card statements—cannot be loaded by URL (even though EagleFiler uses Safari’s persistent cookies). These pages require session state, e.g. entering a password, logging in, and then clicking a link to get to the page. When you try to capture one of these pages, EagleFiler will import the site’s login page, since that’s what the server produces when EagleFiler requests the URL. (An easy way to see that this has happened is to install Growl; EagleFiler will then show a thumbnail preview of each Web page that you capture, so you can see whether it looks right.)

Two ways to import these types of pages are:

Previous Next  Up  Table of Contents  EagleFiler Home