Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(docs) 2048 char limit applies to GET, not POST #27

Open
alexlehm opened this issue Feb 28, 2014 · 2 comments
Open

(docs) 2048 char limit applies to GET, not POST #27

alexlehm opened this issue Feb 28, 2014 · 2 comments

Comments

@alexlehm
Copy link

this is more of a nitpick than an actual issue, the limit of 2048 chars applies to GET, not to POST and the url that is requested by jserrlog is a GET

@TimYi
Copy link
Contributor

TimYi commented Jun 28, 2016

And it is a little bit weard to write request queue to head tag. Though it's inconvenient to write ajax in raw js.

@TimYi
Copy link
Contributor

TimYi commented Jul 1, 2016

@alexlehm in a latest commit, a sendError method is added. Overwrite this method to add post support to your own server. An error object is also added, use error.stack you can record the whole stack trace.
// Send error to server side, default approach is jsErrLog.appendScript.
jsErrLog.sendError = function(i, sn, file_loc, line_no, col_no, ui, info, msg, error) { try { jsErrLog.sendErrorInternal(i, sn, file_loc, line_no, col_no, ui, info, msg, error) } catch (e) { jsErrLog.errorHandler("sendErrorInternal", e); } }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants