Failed - Unexpected token < in JSON at position 0

[haroldtreen]

Failed - Unexpected token < in JSON at position 0

[haroldtreen]

Thanks so much for this bug report @sTywin !

I'm debugging it now and will have an explanation shortly.

[haroldtreen]

I took a deeper look at the seat14c.com/future_ideas pages and they are unfortunately very large.

Each page is ~4Mb. EpubPress has a limit of 10Mb for any content sent.

Why the error?

nginx was being used to enforce that limit - it responds with html, but the extension expects json responses. So when it goes to parse the response it has a bad time.

Results

I've made it so that requests > 10 Mb and < 30 mb will get a friendlier error. Will need an extension update to catch the error for all cases.

I'm going to mark this as closed. Getting all those pages to work with EpubPress would require boosting the limit to

23 * 4Mb = 92 Mb

Allowing books that are ~100Mb large would degrade service for everyone and make the service more expensive to run.

Not the conclusion I had hoped for - sorry :(.

A separate issue exists for the JSON parsing bug, so I'll add these details and continue to track progress there.

Thanks again for the detailed bug report!

[sTywin]

Makes sense, thanks for the update. A friendlier error will help.

[bkrlik]

Today I received the same error on all the pages I tried to download, both on Chrome and Firefox.

[bkrlik]

Now it works.

[haroldtreen]

Thanks for the update @bkrlik!

Was off the grid the last few days and something went down 😬

[bkrlik]

Again it's no working :(

[haroldtreen]

Currently experiencing some server issues. Hope to have things back up soon.

Sorry for the inconvenience.

[haroldtreen]

Things are working again. Thanks again for alerting me @bkrlik !

[jeffrechten]

How do we get an updated client to fix this? I'm still running into the same issue.

[haroldtreen]

@jeffrechten
If you're seeing the error it's because too much data is being sent.
The fix would be to log a nice error that says:

Try sending less data...

Could be done in epub-press-js#normalizeErrors. I can do that this weekend, just hasn't been on the top of my priorities.

[jeffrechten]

@haroldtreen Would this be expected for one page of data? ~1200 lines, 110k characters.

[haroldtreen]

@jeffrechten One page doesn't seem like it should be an issue... but it could be? The amount of text on the page isn't what matters as much as the size of the html in the page. Sometimes pages download content in the background, store it in the page but hidden.

Do you have more information?

• What's the page?
• If you inspect the "background page" do you see any error?
  
• If you go into the Network tab and click the book request, is the response?
  

[jeffrechten]

@haroldtreen It's a yammer page I am logged into.

After I select the page for the book and click download, there isn't a books request. Also, the total size is not terribly large: I forced a refresh to capture any cached data.

There are no errors in the console.

[haroldtreen]

@jeffrechten I think you're looking at an inspector for the yammer webpage.

To see what EpubPress is doing you'll need to:

• Go to chrome://extensions
• Enable Developer Mode
  
• Inspect the background page for EpubPress (screenshot in previous comment).

That's where the request should be coming from.

[jeffrechten]

@haroldtreen Okay, I see. Sorry.
Here's what I got:

[haroldtreen]

@jeffrechten Hmmm... so it's not responding with anything? That seems a bit strange...

What's in the Headers tab? Would be curious what the outbound request looks like.
What's the second network request? Doesn't look like anything that EpubPress requests.

This is what the output should look like:

And the Headers:

[haroldtreen]

Published a new version of epub-press-js that catches this error and returns something nicer.

https://www.npmjs.com/package/epub-press-js

Now just need to update the chrome extension.

[jeffrechten]

@haroldtreen I noticed that the request was getting caught by a corporate proxy so that is why it wasn't making it to the server side.