PassMark Logo
Home » Forum

Announcement

Collapse
No announcement yet.

URL Rewrite Problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • URL Rewrite Problem

    We have a web site where many pages use friendly urls e.g. www.excitech.co.uk/products/revit-toolkit.asp. These pages don't actually exist and the server creates the page from a standard page/database and does a URL rewrite so the user sees what they expect.
    Zoom is failing to index these pages and reporting File Not Found.
    Is there something in Zoom we have failed to do?

  • #2
    There should be no problem indexing dynamic pages. Most of our own site is dynamically generated.

    I tried indexing your site from here and didn't have any problems.

    18:13:36 - Start indexing (spider mode) at Fri Jul 26 19:13:36 2013
    19:13:36 - Maximum number of words: 50000
    19:13:36 - Maximum number of files: 5000
    19:13:36 - Will scan files with extensions
    19:13:36 - .php
    19:13:36 - .pdf
    19:13:36 - .html
    19:13:36 - .htm
    19:13:36 - .aspx
    19:13:36 - .asp
    19:13:36 - Spider from: http://www.excitech.co.uk/products/revit-toolkit.asp
    19:13:36 - Web site URL: http://www.excitech.co.uk/products/
    19:13:36 - Estimated RAM required during index process: 166219 KB
    19:13:37 - [DOWNLOAD] Downloading robots.txt file found at http://www.excitech.co.uk/robots.txt
    19:13:38 - Initiating HTTP session (thread #1) ...
    19:13:38 - DL Thread #1, got URL (http://www.excitech.co.uk/products/revit-toolkit.asp) off queue
    19:13:38 - [DOWNLOAD] Downloading file http://www.excitech.co.uk/products/revit-toolkit.asp
    19:13:39 - Index Thread got ready buffer for http://www.excitech.co.uk/products/revit-toolkit.asp (Content-type: HTML text)
    19:13:39 - [QUEUED] Spidering for links on http://www.excitech.co.uk/products/revit-toolkit.asp
    19:13:39 - [QUEUED] Queued URL: http://www.excitech.co.uk/products/default.asp
    ...

    If you can't see the problem, then maybe E-Mail us the log file and I can have a look.

    Comment


    • #3
      Thanks for your help. It seems our server settings did not allow browsing of those pages locally. This is now fixed. We should have thought of that!

      Comment

      Working...
      X