SSR: Accessing the user's loginToken on the server

sacha · December 7, 2016, 8:23am

I’m looking into getting rid of our dependency on fast-render, and it seems like one thing it does is set a cookie that contains the current user’s loginToken, because it’s not accessible on the server otherwise:

github.com

kadirahq/fast-render/blob/master/README.md#security

# Fast Render [![Build Status](https://travis-ci.org/kadirahq/fast-render.svg?branch=master)](https://travis-ci.org/meteorhacks/fast-render)

Fast Render can improve the initial load time of your app, giving you 2-10 times faster initial page loads. It provides the same effect as Server Side Rendering (SSR), but still sends data over the wire to avoid breaking one of Meteor’s core principles.

**Table of Contents**

  - [Demo](#demo)
  - [Usage](#usage)
  - [How Fast Render Works](#how-fast-render-works)
  - [Using Fast Render With Iron Router](#using-fast-render-with-iron-router)
  - [Using Fast Render's route APIs](#using-fast-renders-route-apis)
  - [Security](#security)
  - [Known Issues](#known-issues)
  - [Debugging](#debugging)
  - [Fast Render 2.x vs 1.x](#fast-render-2x-vs-1x)

## Demo

Let's look at a demo. Here is the leaderboard example from [BulletProof Meteor](https://bulletproofmeteor.com). It's written using Meteor and Iron Router:

This file has been truncated. show original

In the linked discussion, there’s a message from Emily Stark that states:

This is very cool! I’m really excited to see experimentation with
storing login tokens in cookies, because that’s something we’ll need to
figure out eventually for server-side rendering.

It doesn’t seem like there have been any further discussion since then, so I would love to know what the current state of things is. Is this a feature that’s on the roadmap, since enabling server-side rendering is pretty important? Any thoughts @benjamn?