如何要求正确填写表单后方可访问数据？（无登录保密网站场景）

Hey there, let's walk through exactly how to build this anonymous, credential-locked content system for your no-login confidential site. Since you don't want any user account ties, we'll anchor access entirely to the passphrase and passcode users submit with their content.

Instead of tying content to user accounts, we'll link each submission directly to the unique combination of passphrase + 5-digit passcode the user provides. When someone wants to access the content later, they'll need to input that exact combination to unlock it.

1. Form Submission & Secure Storage #

First, handle the user's submission while keeping things secure (no plaintext credentials!):

• Frontend Validation: Add basic checks to ensure the passcode is a 5-digit number (use HTML5's pattern="[0-9]{5}" or a quick JS check) and that all required fields (title, info, passphrase, passcode) aren't empty. This saves unnecessary backend requests.
• Backend Processing & Storage: When the form hits your server, hash the combined passphrase + passcode before storing it with the content. Never store plaintext credentials—hashing makes sure even if your database is compromised, attackers can't reverse-engineer the access codes.

Here's a simplified example using Node.js/Express and MongoDB:

const bcrypt = require('bcrypt');
const saltRounds = 10; // Higher = more secure, slightly slower

// Handle content submission
app.post('/submit-content', async (req, res) => {
  const { title, info, passphrase, passcode } = req.body;
  
  // Combine and hash the access credentials
  const combinedCredentials = `${passphrase}${passcode}`;
  const hashedCredentials = await bcrypt.hash(combinedCredentials, saltRounds);

  // Store the content + hashed credentials (NO user IDs!)
  await db.collection('confidential-content').insertOne({
    title,
    info,
    hashedCredentials,
    createdAt: new Date()
  });

  // Critical reminder for the user—no account means no password reset!
  res.send('Content submitted successfully. *Please save your passphrase and passcode—you won’t be able to recover them if lost.*');
});

2. Content Access & Validation #

Next, build the flow for users to retrieve their content:

• Access Form: Create a simple form where users input their passphrase, passcode, and optionally the title of their content (this helps narrow down matches if multiple submissions have similar credentials).
• Backend Validation Logic: Fetch potential matching records, then verify that the submitted credentials match the stored hash.

Example access endpoint:

// Handle content access requests
app.post('/access-content', async (req, res) => {
  const { passphrase, passcode, title } = req.body;
  const submittedCredentials = `${passphrase}${passcode}`;

  // Query for content: use title if provided to narrow results
  const query = title ? { title } : {};
  const matchingRecords = await db.collection('confidential-content').find(query).toArray();

  // Check each record for a credential match
  let unlockedContent = null;
  for (const record of matchingRecords) {
    const isMatch = await bcrypt.compare(submittedCredentials, record.hashedCredentials);
    if (isMatch) {
      unlockedContent = { title: record.title, info: record.info };
      break;
    }
  }

  if (unlockedContent) {
    res.json(unlockedContent);
  } else {
    res.status(403).send('Invalid passphrase or passcode—cannot access content.');
  }
});

3. Security & Experience Improvements #

• Rate Limiting: Add rate limiting to your /access-content endpoint (e.g., using express-rate-limit for Node.js) to block brute-force attacks. Limit users to 5-10 attempts per minute.
• Frontend Obscuration: For extra peace of mind, encrypt the credentials on the frontend before sending them to the backend (e.g., using AES encryption). This adds a layer of protection against eavesdropping.
• Content Expiry: Optional—add an expiry date to each submission so old content is automatically deleted, reducing the risk of stale sensitive data hanging around.
• Clear User Messaging: Repeat the reminder that credentials can't be recovered—users need to write them down or store them securely.

内容的提问来源于stack exchange，提问作者Sheldon C