summaryrefslogtreecommitdiffstats
path: root/netwerk
Commit message (Collapse)AuthorAgeLines
* Issue #1656 - Part 6: Clean up the build filesMoonchild2020-09-23-39/+0
|
* Issue #1656 - Part 4: Manual cleanupMoonchild2020-09-23-6/+0
|
* Issue #1656 - Part 4: Tackle *.idl, *.css, *.ipdlh, *.webidl, *.ccMoonchild2020-09-23-14/+0
|
* Issue #1656 - Part 3: Nuke more vim config lines in the tree.Moonchild2020-09-23-85/+0
| | | | Another S&R run with some smarter matching.
* Issue #1656 - Part 1: Nuke most vim config lines in the tree.Moonchild2020-09-23-58/+0
| | | | | | Since these are just interpreted comments, there's 0 impact on actual code. This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are a few others scattered around which will be removed manually in a second part.
* [WebRTC] Stop putting addresses in the cookie chunk.Michael Tuexen2020-07-29-0/+42
| | | | | | | | | | | When using AF_CONN addresses, don't put these in the COOKIE chunk. For these addresses it is possible to reconstruct them locally. Conceptually, addresses are something to be shared with the peer, but in the case of AF_CONN this might not be the case. Therefore, zero then out. Thanks to Natalie Silvanovich of Google Project Zero for finding and reporting the issue.
* [xpcom] Make Base64 compatible with ReadSegments() with small buffers.Andrea Marchesini2020-07-29-0/+96
|
* [network/dom] Improve sanitization of download filenames.Moonchild2020-07-29-0/+12
|
* [network] Use query and ref lengths if available in nsStandardURL.Moonchild2020-07-10-2/+6
|
* Merge pull request #1556 from adeshkp/patch-18Moonchild2020-05-19-0/+1
|\ | | | | Include MDNSResponderOperator.h in libmdns/nsDNSServiceDiscovery.h for Mac
| * Issue #80 - Include MDNSResponderOperator.h in ↵adeshkp2020-05-18-0/+1
| | | | | | | | | | libmdns/nsDNSServiceDiscovery.h for Mac This is needed for forward declaration of `BrowseOperator` and `RegisterOperator`.
* | Issue #80 - Add nsSocketTransportService2.h to ThrottleQueue.cppGaming4JC2020-05-18-0/+1
|/
* Issue #80 - De-unify netwerk/wifiMoonchild2020-05-18-9/+6
|
* Issue #80 - De-unify netwerk/streamconvMoonchild2020-05-18-3/+5
|
* Issue #80 - De-unify netwerk/srtpMoonchild2020-05-18-1/+1
|
* Issue #80 - De-unify netwerk/socketMoonchild2020-05-18-2/+3
|
* Issue #80 - De-unify netwerk/protocol/httpMoonchild2020-05-18-15/+17
|
* Issue #80 - De-unify netwerk/protocol/resMoonchild2020-05-18-1/+1
|
* Issue #80 - De-unify netwerk/protocol/ftpMoonchild2020-05-18-1/+5
|
* Issue #80 - De-unify smaller netwerk/protocol componentsMoonchild2020-05-17-5/+8
| | | | | | | | - data - device - file - viewsource - wyciwyg
* Issue #80 - De-unify netwerk/protocol/aboutMoonchild2020-05-17-1/+4
|
* Issue #80 - De-unify netwerk/ipcMoonchild2020-05-17-1/+3
|
* Issue #80 - De-unify netwerk/dnsMoonchild2020-05-17-7/+4
|
* Issue #80 - De-unify netwerk/cookieMoonchild2020-05-17-4/+1
|
* Issue #80 - De-unify netwerk/cache2Moonchild2020-05-17-6/+8
|
* Issue #80 - De-unify netwerk/cacheMoonchild2020-05-17-1/+3
|
* Issue #80 - De-unify netwerk/baseMoonchild2020-05-17-3/+31
|
* [WebRTC] Port some upstream sctp fixesMoonchild2020-05-06-7/+22
| | | | | - add SCTP auth token boundary check. - turn off SCTP auth and address reconfiguration.
* Issue #1505 - Part 3: Make native mode actually native again.wolfbeast2020-04-05-4/+36
|
* Issue #1505 - Part 2: Store application build ID in nsHttpHandlerwolfbeast2020-04-05-16/+13
| | | | | Since we're needing to reuse this several times, it makes it simpler to just get it once in init and storing it.
* Issue #1505 - Rebuild application version stringwolfbeast2020-04-05-37/+46
| | | | | | | To respond dynamically to the pref change, the mAppVersion string needs to be rebuilt. Includes some minor improvements for corner cases and removes leftover b2g junk.
* Issue #1280 - Un-bust certerror pages and ForgetAboutSitewolfbeast2020-03-31-12/+1
|
* Merge pull request #1500 from MoonchildProductions/1280Moonchild2020-03-29-21/+0
|\ | | | | Remove HPKP
| * Issue #1280 - Part 1: Remove HPKP components.wolfbeast2020-03-28-21/+0
| | | | | | | | | | This also removes leftover plumbing for storing preload information in SiteSecurityService since no service still uses it.
* | Issue #1473 - Fix building `%OS_SLICE%` on non-Windows platformsJustOff2020-03-24-5/+22
|/
* [network] Cherry-pick various sctp lib upstream fixes.wolfbeast2020-03-18-9/+24
|
* Issue #1482 - Give dynamic SSUAO rules priority over static onesJustOff2020-03-15-7/+19
|
* Issue #1053 - Remove no longer used function and modules from ↵JustOff2020-03-11-30/+0
| | | | `UserAgentUpdates.jsm`
* Merge pull request #1476 from JustOff/PR_ssuao_os_sliceNew Tobin Paradigm2020-03-10-1/+4
|\ | | | | Add `%OS_SLICE%` macro to SSUAO to refine OS info
| * Issue #1473 - Add `%OS_SLICE%` macro to SSUAO to refine OS infoJustOff2020-03-10-1/+4
| |
* | Issue #1474 - Prevent the cp detection from starting if preffed off.wolfbeast2020-03-07-4/+4
|/ | | | | | | | When setting up connectivity, e.g. with new network detection, the pref wouldn't be checked (or honored), resulting in spurious startup calls despite being preffed off. This fixes that. Resolves #1474
* Issue #1053 - Remove android support from ↵Matt A. Tobin2020-02-22-55/+0
| | | | netwerk/protocol/http/nsHttpHandler.cpp
* Issue #1053 - Remove android support from netwerkMatt A. Tobin2020-02-22-1404/+16
|
* [Network] Bump http channel default Firefox CompatMode init value.wolfbeast2020-02-14-1/+1
|
* Issue #1395 - Remove FlyWeb ServiceMatt A. Tobin2020-02-06-15/+0
|
* Fix preprocessor directive in UserAgentUpdates.jsmNew Tobin Paradigm2020-02-02-1/+1
|
* Issue #65 - Remove AppConstants from netwerk/Matt A. Tobin2020-02-01-10/+9
|
* Fix whitespace.athenian2002020-01-26-1/+1
|
* Issue #1349 - Stop 2xx FTP responses from causing browser to hang.athenian2002020-01-26-4/+20
| | | | | | LIST and RETR still appear to work as intended on ftp:// URLs after my changes. I wasn't able to test STOR because the browser doesn't appear to support FTP uploads at this time (although our FTP implementation appears perfectly capable of doing an FTP upload.) If I understood the issue correctly, though, what we're doing is ensuring that we receive a preliminary 100 response from the FTP server for a given action before jumping to the 200 code describing what we do if the action was completed. Even though it makes no logical sense for a server to say an action was completed before it was initiated, someone could write a really annoying FTP server that takes advantage of this fact to crash the browser if they wanted.
* No issue - Fix unsafe http methods on HTTP/2 with TLSv1.3 0RTT.wolfbeast2020-01-18-2/+6
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-27 21:12:15 +0000