nodeSolidServer / nodeSolidServer/node-solid-server

NSS does not redirect from /foo to /foo/ for private resources (from command line)

Open
#1,589 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

I have myPod/private/ and myPod/public/ folders.

The code below, after login, gives 200 if the target is myPod/private/ but a 401 if the target is myPod/private. However both myPod/public and myPod/public/ return a folder list.

import {SolidNodeClient} from './';                                             
const client = new SolidNodeClient();                                           
                                                                                
const target = "https://jeff-zucker.solidcommunity.net/private";                
                                                                                
async function test(credentials){                                               
  let session = await client.login( credentials );                              
  if( session.isLoggedIn ){                                                     
    let r = await client.fetch( target );                                       
    console.log(  r.status  );
  }                                                                             
  else {                                                                        
    console.log(  'Could not log in!'  );                                       
  }                                                                             
}                                                                               
                                                                                
test({                                                                          
  username:'jeff-zucker',                                                       
  idp:'https://solidcommunity.net',                                             
  password:'REDACTED'                                                        
})    

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report provides a JavaScript command-line reproduction using SolidNodeClient; start by running it against the private and public resource URLs with and without the trailing slash. Done means the private resource behaves consistently for both forms, including after login, without the reported 401 response.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.