Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

callback function is not called as should

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript

Research direction

Start by tracing HTTPDigest.prototype.request in the shown request flow, including http.request and _handleResponse, when the code is browserified. Reproduce the 401 digest-auth response in the browser and compare callback behavior before and after the credentials popup. Done means the callback is invoked consistently without requiring an extra credentials-dialog action.

Written by the indexing model from the issue text.

Description

Server is a digest auth node.

HTTPDigest.prototype.request = function (data, options, callback) {
    var self = this;
    http.request(options, function (res) {
      self._handleResponse(data, options, res, callback);
    }).end();
  };

if I do this in node I receive a 401 with nonce in order than to make the second request (the real one)
when browserified the a popup for the credentials is poped and the the function is not called but only after you click ok or cancel button.

Dominant language
JavaScript
Stars
245
Forks
104
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from browserify/http-browserify

All issues in browserify/http-browserify

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.