Skip to content

issues Search Results · repo:browserify/http-browserify language:JavaScript

Filter by

39 results
 (54 ms)

39 results

inbrowserify/http-browserify (press backspace or delete to remove)

Is it possible to upgrade the dependency Base64 from the current ~0.2.0 to latest (1.1.0)? I have verified that Base64 is really only used once in http-browserify code and changing versions wouldn t break ...
  • AshishShanker
  • Opened 
    on Apr 13, 2022
  • #107

When doing a HEAD request with the http library, the javascript just crashes and does not give me any answers. I tried debugging it myself and found that the library uses fetch to fetch the head. The ...
  • KAYLukas
  • Opened 
    on Feb 9, 2017
  • #104

Since https://github.com/nodejs/node/commit/235036e7faa537469c3600850bdd533c095c392a, node has been updated to return HTTP status codes to match the IANA ones. Please update your code so they match. e.g: ...
  • ghost
  • Opened 
    on Nov 12, 2016
  • #102

@substack doesn t appear to have time to maintain this; perhaps you could put out a call for a maintainer? There are a large number of open PRs and issues, but no commits for a long time.
  • elyobo
  • Opened 
    on Jun 29, 2016
  • #99

Hi, I use node-fetch in a reacts + rails project. I use https://github.com/shakacode/react_on_rails to glue between reactjs and Rails. Everything works fine except when I do server side rendering it complains ...
  • ywen
  • 3
  • Opened 
    on Nov 20, 2015
  • #97

If not specified, http-browserify sets the protocol to window.location.protocol. This differs from the behavior of Node (see https://nodejs.org/api/http.html#http_http_request_options_callback ). I assume ...
  • recursify
  • 2
  • Opened 
    on Oct 29, 2015
  • #96

Request is missing setNoDelay method that exists on the node.js version. Some libs (e.g. EventSource) call this method.
  • elado
  • Opened 
    on Sep 11, 2015
  • #95

Doesn t seem to work on mobile
  • kingzbauer
  • 1
  • Opened 
    on Sep 4, 2015
  • #94

If window.location.href is http://localhost:8000/app/#/, one would expect a GET to ./ping to be a request to http://localhost:8000/app/ping. At least, that s how XMLHttpRequest behaves. But instead it ...
  • lukehorvat
  • 1
  • Opened 
    on Jul 23, 2015
  • #92

I understand HTTP header names are case-insensitive (RFC 2616). I m currently interacting with an API that does not follow protocol, it works via node s https but not browserify s. If you want complete ...
  • vartan
  • Opened 
    on Jul 17, 2015
  • #91
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue search results · GitHub