digital-marketing-

```javascript
const { Router } = require('{{ PACKAGE_NAME }}/core');

const router = new Router({
  name: 'production-routing-config',
  routes: [
    {
      path: '/api/*',
      proxy: {
        target: 'https://api.example.com',
        timeout: 5000,
        headers: {
          'X-Upstream-Timeout': '5s'
        }
      }
    },
    {
      path: '/*',
      redirect: {
        status: 301,
        to: 'https://example.com$1'
      }
    },
    {
      path: '/static/*',
      cache: {
        maxAge: 3600,
        staleWhileRevalidate: 1800,
        vary: ['Accept-Encoding']
      },
      headers: {
        'Cache-Control': 'public, max-age=3600, stale-while-revalidate=1800'
      }
    },
    {
      path: '/*',
      status: 404,
      serve: '/404.html',
      headers: {
        'Content-Type': 'text/html'
      }
    }
  ],
  headers: {
    'X-Content-Type-Options': 'nosniff',
    'X-Frame-Options': 'DENY',
    'Strict-Transport-Security': 'max-age=31536000; includeSubDomains; preload'
  }
});

module.exports = router;
```

### Explanation of the configuration:

1. **API Proxying**: All requests to `/api/*` are forwarded to `https://api.example.com` with a 5-second timeout. This ensures backend services remain responsive during traffic spikes.

2. **HTTPS Enforcement**: The router automatically redirects all HTTP traffic to HTTPS using a 301 permanent redirect, which is crucial for SEO and security compliance.

3. **Static Asset Caching**: Assets under `/static/*` are cached for 1 hour (3600 seconds) with a stale-while-revalidate window of 30 minutes (1800 seconds). This reduces origin server load while ensuring fresh content delivery.

4. **Custom 404 Handling**: Unmatched routes serve a custom `404.html` page, improving user experience and brand consistency.

5. **Security Headers**: Essential security headers are added to every response, protecting against common web vulnerabilities like clickjacking and MIME sniffing.

This configuration leverages EdgeJS's ability to handle routing logic programmatically, making it easier to test, version control, and deploy alongside your application code. The router can be deployed using the EdgeJS CLI with `edgejs deploy production-routing-config.js`.