old "last-event-id" used on reconnect

[mbieser]

I am seeing the "last-event-id" header used on reconnect, but everytime it reconnects, it's using the original "last-event-id" value, even when subsequent events had been processed since the original connect.

scenario:

• initialize eventsource with a last-event-id
• begin listening and process some events
• connection drops and reconnects using original "last-event-id"

Should be using the last event's id!

[aslakhellesoy]

@mbieser I'm not sure I understand what you're doing without seeing some code. Are you initialising an EventSource object doing something like this?

var eventSourceInitDict = {headers: {'last-event-id': someId}};
var es = new EventSource(url, eventSourceInitDict);

[mbieser]

@aslakhellesoy Yes. Initializing the Eventsource with a last-event-id, then receive some events, then on disconnect+reconnect the eventsource reconnects with the original last-event-id header, not the latest value of lastEventId.

[aslakhellesoy]

Gotcha. Fixed in 0.0.9. Let me know if that solves your problem.

[aslakhellesoy]

Note that in order for this to work you must specify the header as defined in the W3C spec: Last-Event-ID. It's case sensitive - last-event-id will not work.

[mbieser]

Works! Thanks for the quick patch.

--Mike