jquery.ajax始终以GET传参，Node.js新手跨服务器架构方案咨询

Hey there! As someone who’s navigated similar tech stack transitions before, I totally get the learning curve when shifting from mixed PHP/client-side code to a separate Node.js setup. Let’s walk through practical, actionable solutions to streamline your current workflow:

1. Use a Reverse Proxy to Unify Your Services #

Running Node.js and Apache on separate ports creates cross-origin headaches and complicates client-side requests. A reverse proxy (like Nginx or even Apache itself) can route traffic to the right service based on URL paths, making everything appear to come from a single port.

For example, here’s a simplified Nginx config snippet that sends /api/* requests to your PHP/Apache server and all other traffic to your Node.js app:

server {
    listen 80;
    server_name localhost;

    # Route API requests to Apache/PHP
    location /api/ {
        proxy_pass http://localhost:8080; # Replace with your Apache port
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }

    # Route all other requests to Node.js
    location / {
        proxy_pass http://localhost:3000; # Replace with your Node.js port
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

This way, your client code only needs to target localhost without worrying about port numbers, and you’ll avoid CORS issues entirely.

2. Gradually Migrate PHP Logic to Node.js #

Since you’re new to Node.js, you don’t have to rewrite everything at once. Start by moving simple PHP endpoints (like basic data fetching or form submissions) to Node.js using a framework like Express. Over time, you can phase out Apache entirely as you migrate more complex business logic.

For example, a basic Express endpoint to replace a PHP API might look like this:

const express = require('express');
const app = express();

app.get('/api/users', (req, res) => {
    // Replace this with your actual database query (use mysql2, pg, etc.)
    const users = [{ id: 1, name: 'John Doe' }];
    res.json(users);
});

app.listen(3000, () => console.log('Node.js server running on port 3000'));

This approach lets you learn Node.js incrementally while reducing your dependency on Apache.

3. Use Node.js Template Engines for "Mixed" Style Development #

If you miss the convenience of mixing logic with client-side code (like you did with PHP), Node.js has great template engines that replicate that workflow. Tools like EJS, Pug, or Handlebars let you embed JavaScript logic directly in your HTML templates, rendered server-side by Node.js.

For example, an EJS template that lists users will feel familiar if you’re used to PHP:

<ul>
    <% users.forEach(user => { %>
        <li><%= user.name %></li>
    <% }) %>
</ul>

This eliminates the need for AJAX for basic page rendering and keeps your workflow closer to what you’re comfortable with.

4. Temporary Fix: CORS Configuration (If You Want to Keep Separate Servers) #

If you need to stick with separate servers for now, you can fix cross-origin issues by enabling CORS in your Node.js app. Install the cors package and add it as middleware:

npm install cors

const cors = require('cors');
app.use(cors({ origin: 'http://localhost:8080' })); // Allow requests from Apache's port

This is a quick band-aid, but I’d recommend moving to a reverse proxy long-term for a cleaner, more scalable setup.

Take it step by step—start with the reverse proxy to simplify your client requests, then experiment with template engines or gradual migration to Node.js. You’ve got this!

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