History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SRC-432
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: James Davis
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Selenium Remote Control

403 Forbidden for Proxy error" does not appear when running java client with -userExtensions

Created: 26/Feb/08 12:21 PM   Updated: 12/Aug/08 05:35 PM
Component/s: Server
Affects Version/s: 0.9.0, 0.9.2
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment:
1. Windows XP Pro, Java 1.6
2. Kubuntu 7.10 "Gutsy Gibbon", Java 1.6


 Description  « Hide
When the selenium server is started with the -userExtensions switch, a 403 Error does not appear when directly accessing "http://localhost:4444/selenium-server" in the browser.

Instead the contents of the file system are exposed. So far, only able to replicate when using the -userExtensions switch.

Found in both 0.9.0 and 0.9.2.

STEPS TO REPRODUCE
1. Run java -jar selenium-server.jar -userExtensions user-extensions.js.
2. Open browser, paste http://localhost:4444/selenium-server into a browser address bar. The contents of the file system will display. Expecting the below error message instead.
3. Stop java client.
4. Run java -jar selenium-server.jar.
5. Repeat step 2, expected 403 error appears.

EXPECTED ERROR
HTTP ERROR: 403
Forbidden for Proxy
RequestURI=/selenium-server/


 All   Comments   Work Log   Change History      Sort Order:
Andre - 14/Mar/08 08:10 PM
Here's another manifestation of this bug. Running on linux with v 0.9.1

$ java -classpath selenium-server.jar org.openqa.selenium.server.SeleniumServer 2>/dev/null &
$ wget http://localhost:4444/selenium-server
    gives 403

$ java -classpath /tmp:selenium-server.jar org.openqa.selenium.server.SeleniumServer 2>/dev/null &
$ wget http://localhost:4444/selenium-server
    gives 200 and a list of files.

All it takes is *one* directory in the classpath. Maybe that's the intended behavior?