Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327084 - Cannot connect to InfoCenters with index.jspx on the top.
Summary: Cannot connect to InfoCenters with index.jspx on the top.
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M3   Edit
Assignee: Chris Austin CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 320667
Blocks:
  Show dependency tree
 
Reported: 2010-10-06 06:26 EDT by Evgeny Avtsin CLA
Modified: 2010-10-21 11:44 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Evgeny Avtsin CLA 2010-10-06 06:26:13 EDT 
Build Identifier: Version:3.6.0 Build ID:I20100608-0911

The infocenter URL is automatically extended for the default index.jsp.
The user cannot connect InfoCenter with different main file.

An option to specify the name of the index file should be added or the system should check "jspx"-extension as well.

Reproducible: Always

Steps to Reproduce:
1.Windows->Preferences->Help->Content->New
2.Determine a new information center:
   Name: MTA
   Host: lirr42.mta.info
   Path: /sfweb/faces
   Press Ok
3.Press "Test connection"
   "Connection Status: Successful."
4.Help->Search
   Select "Some network help is unavailable"
   Unavailable Sites:
     http://lirr42.mta.info:80/sfweb/faces/index.jsp 

5. Try entering "http://lirr42.mta.info/sfweb/faces/index.jsp" in the browser -> 404 Not Found
   "http://lirr42.mta.info/sfweb/faces/index.jspx" works fine.
Comment 1 Chris Austin CLA 2010-10-06 09:59:34 EDT 
This issue will be resolved by changes we make in bug 320667 - we will be checking the toc (rather then index.jsp) for the validity of the infocenter.
Comment 2 Chris Austin CLA 2010-10-21 11:43:31 EDT 
This bug has been resolved indirectly by the changes in bug 320667.