Closed Bug 40453 Opened 25 years ago Closed 24 years ago

reload doesn't work well after changing fold permission

Categories

(Core :: Networking: Cache, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: czhang, Assigned: neeti)

Details

load 5/24 build 1. set permission of your web fold for example "bugs" to be 0755, other people readable. from browser, you are able to see the content of the fold 2. change fold permission to be 0711, disable viewable from other people. 3. go to "bugs" from browser. hit enter, you see the content of the fold, hit reload button, it is saying "forbidden", from location box, hit enter again,you still see the content, no matter how hard you try to reload, you still get the content of the fold. this could have security problem if you set the mode of the fold not viewable by other people initially, this won't happen. also either case works fine on 4.7 expected: hit reloading after changing should permanently change the display from browser.
-> Networking: Cache
Component: Browser-General → Networking: Cache
Sorry for the spam. New QA Contact for Browser General. Thanks for your help Joseph (good luck with the new job) and welcome aboard Doron Rosenberg
QA Contact: jelwell → doronr
setting default owner
Assignee: asa → gordon
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: doronr → tever
I am not able to reproduce the problem. I viewed a directory /export2/pnunn/neeti_test/ in the browser, which had permissions set as 755. Then pnunn changed the permissions to 711. When I hit reload, the page stays the same, but the message in the console box says it could not load the page. Now, if you try opening one the files inside the folder, they won't open. Also, if you browse to some other site and come back to /export2/pnunn/neeti_test/, it won't load it. Next, if the permissions were changed back to 755, I could view the folder and also the files inside. Neeti
Assignee: gordon → neeti
Status: NEW → ASSIGNED
Target Milestone: --- → M17
I am not able to reproduce the problem. I performed the steps as described above. Neeti
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
verified wfm
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.