I Use This!
Very High Activity

News

Analyzed 17 days ago. based on code collected 18 days ago.
Posted 5 days ago by Air Mozilla
Reunión bi-semanal para hablar sobre el estado de Mozilla, la comunidad y sus proyectos. Bi-weekly meeting to talk (in Spanish) about Mozilla status, community and...
Posted 5 days ago by Barbara Bermes
Last year, we introduced Firefox Focus, a new browser for the iPhone and iPad, designed to be fast, simple and always private. A lot has happened since November; and more than ever before, we’re seeing consumers play an active role in trying to ... [More] protect their personal data and save valuable megabytes on their data plans. While we knew that Focus provided a useful service for those times when you want to keep your web browsing to yourself, we were floored by your response  – it’s the highest rated browser from a trusted brand for the iPhone and iPad, earning a 4.6 average rating on the App Store. Today, I’m thrilled to announce that we’re launching our Firefox Focus mobile app for Android. Like the iPhone and iPad version, the Android app is free of tabs and other visual clutter, and erasing your sessions is as easy as a simple tap.  Firefox Focus allows you to browse the web without being followed by tracking ads which are notoriously known for slowing down your mobile experience.  Why do we block these ad trackers? Because they not only track your behavior without your knowledge, they also slow down the web on your mobile device. Check out this video to learn more:   New Features for Android For the Android release of Firefox Focus, we added the following features: Ad tracker counter – For the curious, there’s a counter to list the number of ads that are blocked per site while using the app. Disable tracker blocker – For sites that are not loading correctly, you can disable the tracker blocker to quickly take care of it and get back to where you’ve left off. Notification reminder – When Focus is running in the background, we’ll remind you through a notification and you can easily tap to erase your browsing history. For Android users we also made Focus a great default browser experience. Since we support both custom tabs and the ability to disable the ad blocking as needed, it works great with apps like Facebook when you just want to read an article without being tracked. We built Focus to empower you on the mobile web, and we will continue to introduce new features that make our products even better. Thanks for using Firefox Focus for a faster and more private mobile browsing experience.   Firefox Focus Settings View You can download Firefox Focus on Google Play and in the App Store. The post Firefox Focus New to Android, blocks annoying ads and protects your privacy appeared first on The Mozilla Blog. [Less]
Posted 5 days ago by Camelia Badau
Hello Mozillians, We are happy to let you know that Friday, June 23rd, we are organizing Firefox 55 Beta 4 Testday. We’ll be focusing our testing on the following new features: Screenshots and Simplify Page. Check out the detailed instructions via ... [More] this etherpad. No previous testing experience is required, so feel free to join us on #qa IRC channel where our moderators will offer you guidance and answer your questions. Join us and help us make Firefox better! See you on Friday! [Less]
Posted 5 days ago by Pascal Chevrel
Firefox Nightly users, thanks to the telemetry and crash reports they send to Mozilla, are an amazing help to Firefox developers. The aggregated data sent by our community is extremely useful and allows spotting performance or stability regressions ... [More] at the earliest stages of development. It probably can’t be emphasized enough how just using Nightly is a great way to get involved in Mozilla. That said, we have in our Nightly community people that also actively hunt and report bugs and regressions and provide us detailed feedback, usually via the opening of a bug report in Bugzilla. These people are our core community, our first line of defense against regressions, they allow us to ship faster and better software and many of them have been involved in Mozilla and Firefox for a long time. “Have you filed a bug?” is something you often hear open source developers say to people that report them some anomaly or regression, and for the majority of our users, this sounds like a complicated process. Just explaining the bug they experience in terms that make the bug report actionable by the developer that will fix it is a skill in itself. And this is where our core community of power-users on Nightly shines, they have this skill. But what if the reporter has these skills but is not comfortable communicating in English because it is not her native language? Yes, language can also be a barrier to giving feedback… A few days ago, a mozillian from our Spanish community (web developer in an IT company in Spain), sent me an email about a regression he was experiencing at work with nightly in the last days. This is the story I want to tell because it illustrates how powerful community work in open source can be and how lucky Mozilla is to have a dedicated global community. Fernando, or StripTM as we know him in the Mozilla Hispano community, sent me an email about a major performance regression with forms on a page they have on their intranet, clicking in a form field would freeze the browser for seconds, and he wanted to know if I had heard about it. I didn’t so I asked him if there was a way I could see this page. Intranets are tricky, the content there is by definition not public. But StripTM being a Web developer, he emailed me a reduced anonymized version of the page so as that I could test locally if I could see the bug and yes, I was experiencing it as well. Since StripTM is not always comfortable writing bug reports in English, I did it for him and filed bug 1372843 a week ago and attached his test case. I fired up mozregression and found out that the bug was caused by the recent activation of Form Autofill in Nightly (see our article Preview Form Autofill in Firefox Nightly). In a nutshell, the performance problem was caused by the fact that this intranet page had 170(!) forms and our heuristics were cycling through all of the input fields in the page instead of only  the ones for the form we had clicked in. All in all, it took a total of 3 days to discover the performance problem, file a bug and get a patch for it in mozilla-central. This is what happens when you can put passionate and skilled volunteers in contact with our equally passionate and skilled staff! So thank you Fernando for using Nightly all these years and yes, the publishing date of this post is also a way for us to thank you for your involvement in Mozilla and wish you a happy birthday! [Less]
Posted 5 days ago by Pascal Chevrel
Firefox Nightly users, thanks to the telemetry and crash reports they send to Mozilla, are an amazing help to Firefox developers. The aggregated data sent by our community is extremely useful and allows spotting performance or stability regressions ... [More] at the earliest stages of development. It probably can’t be emphasized enough how just using Nightly is a great way to get involved in Mozilla. That said, we have in our Nightly community people that also actively hunt an report bugs and regressions and provide us detailed feedback, usually via the opening of a bug report in Bugzilla. These people are our core community, our first line of defense against regressions, they allow us to ship faster and better software and many of them have been involved in Mozilla and Firefox for a long time. “Have you filed a bug?” is something you often hear open source developers say to people that report them some anomaly or regression, and for the majority of our users, this sounds like a complicated process. Just explaining the bug they experience in terms that make the bug report actionable by the developer that will fix it is a skill in itself. And this is where our core community of power-users on Nightly shines, they have this skill. But what if the reporter has these skills but is not comfortable communicating in English because it is not her native language? Yes, language can also be a barrier to giving feedback… A few days ago, a mozillian from our Spanish community (web developer in an IT company in Spain), sent me an email about a regression he was experiencing at work with nightly in the last days. This is the story I want to tell because it illustrates how powerful community work in open source can be and how lucky Mozilla is to have a dedicated global community. Fernando, or StripTM as we know him in the Mozilla Hispano community, sent me an email about a major performance regression with forms on a page they have on their intranet, clicking in a form field would freeze the browser for seconds, and he wanted to know if I had heard about it. I didn’t so I asked him if there was a way I could see this page. Intranets are tricky, the content there is by definition not public. But StripTM being a Web developer, he emailed me a reduced anonymized version of the page so as that I could test locally if I could see the bug and yes, I was experiencing it as well. Since StripTM is not always comfortable writing bug reports in English, I did it for him and filed bug 1372843 a week ago and attached his test case. I fired up mozregression and found out that the bug was caused by the recent activation of Form Autofill in Nightly (see our article Preview Form Autofill in Firefox Nightly). In a nutshell, the performance problem was caused by the fact that this intranet page had 170(!) forms and our heuristics were cycling through all of the input fields in the page instead of only  the ones for the form we had clicked in. All in all, it took a total of 3 days to discover the performance problem, file a bug and get a patch for it in mozilla-central. This is what happens when you can put passionate and skilled volunteers in contact with our equally passionate and skilled staff! So thank you Fernando for using Nightly all these years and yes, the publishing date of this post is also a way for us to thank you for your involvement in Mozilla and wish you a happy birthday! [Less]
Posted 5 days ago by Daniel Stenberg
The c-ares project may not be very fancy or make a lot of noise, but it steadily moves forward and boasts an amazing 95% code coverage in the automated tests. Today we release c-ares 1.13.0. This time there’s basically three notable things to take ... [More] home from this, apart from the 20-something bug-fixes. CVE-2017-1000381 Due to an oversight there was an API function that we didn’t fuzz and yes, it was found out to have a security flaw. If you ask a server for a NAPTR DNS field and that response comes back crafted carefully, it could cause c-ares to access memory out of bounds. All details for CVE-2017-1000381 on the c-ares site. (Side-note: this is the first CVE I’ve received with a 7(!)-digit number to the right of the year.) cmake Now c-ares can optionally be built using cmake, in addition to the existing autotools setup. Virtual socket IO If you have a special setup or custom needs, c-ares now allows you to fully replace all the socket IO functions with your own custom set with ares_set_socket_functions. [Less]
Posted 5 days ago by Corey Richardson
Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust ... [More] or send us a pull request. Want to get involved? We love contributions. This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR. Updates from Rust Community News & Blog Posts RustConf 2017 tickets are now available. encoding_rs, a new character encoding conversion library written in Rust, has landed in nightly Firefox. Bugs you'll probably only have in Rust. Why not to use Rust. Algorithms cookbook in Rust. Implementing cooperative multitasking in Rust. Switching from C++ to Rust. Graphics by squares: a gfx-rs tutorial. Rustfmt releases. There are some significant changes happening to Rustfmt. Here is what you need to know. System programming in Rust: beyond safety. Writing a LALR(1) parser generator in Rust. hyper v0.11 is released. This week in Redox 22. This week in Servo 104. Crate of the Week This week's crate is include_dir, a crate that lets you include entire directory contents in your binary – like include_str!, but on steroids. Thanks to Michael Bryan for the suggestion! Submit your suggestions and votes for next week! Call for Participation Always wanted to contribute to open-source projects but didn't know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started! Some of these tasks may also have mentors available, visit the task page for more information. [easy] rust: Guard types should implement more traits. walkdir: Add Error docs to methods that return Result. walkdir: Default to generating constified enums, rather than generating Rust enums. walkdir: Change OsString args in sort_by to OsStr. walkdir: Remove re-export of is_same_file. walkdir: Document why unwraps won't fail. walkdir: Make skip_current_dir and filter_entry inherent methods. walkdir: Link references to std in docs. walkdir: Add build badges to Cargo.toml. walkdir: Implement Debug for WalkDir, Iter and IterFilterEntry. walkdir: Correct errors in WalkDir type docs. walkdir: Document that Iter and IterFilterEntry are the result of trait methods. walkdir: Add links to other walkdir items in WalkDirIterator docs. walkdir: Add links to other walkdir items in Iter and IterFilterEntry docs. walkdir: Add links to other walkdir items in DirEntry docs. walkdir: Add example for content_first. rust-cookbook: Use filter_entry in walkdir examples. [easy] rust-bindgen: Default to generating constified enums, rather than generating Rust enums. [less-easy] rust-bindgen: Rewrite is_unsized as either a graph traversal or fix-point analysis. [less-easy] rust-bindgen: Rewrite can_derive_debug as either a graph traversal or fix-point analysis. [less-easy] rust-bindgen: Rewrite can_derive_copy[_in_array] as either a graph traversal or fix-point analysis. [less-easy] rust-bindgen: Rewrite has_vtable checks as either graph traversal or fix-point analysis. If you are a Rust project owner and are looking for contributors, please submit tasks here. Updates from Rust Core 122 pull requests were merged in the last week. overflow-check str index by inclusive (...) ranges float min/max is now pure Rust Ord::{min, max} allocation-less Display for Path and OsStr suggest == on inadvertent assignment in if conditions omit trait errors implied by other errors save-analysis is now JSON only collections is back fix type inference ICE due to missing obligations fix fn pointer coercion ICE use custom cargo/rustc paths when parsing flags cargo stores API tokens in separate, user-private file New Contributors Marco Castelluccio Thomas Lively Wonwoo Choi Approved RFCs Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week: RFC 1974: Prepare global allocators for stabilization. Final Comment Period Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now. This week's FCPs are: [disposition: postpone] Allow extern crate to take a list of crates. [disposition: merge] Stabilize drop order. [disposition: merge] Specify #[repr(transparent)]. [disposition: merge] Conversions from &mut T to &Cell. [disposition: merge] Tiered browser support policy for Rust's web content. New RFCs Experimentally add coroutines to Rust. Add a try_with method to LocalKey, replacing the existing but unstable state method Style RFCs Style RFCs are part of the process for deciding on style guidelines for the Rust community and defaults for Rustfmt. The process is similar to the RFC process, but we try to reach rough consensus on issues (including a final comment period) before progressing to PRs. Just like the RFC process, all users are welcome to comment and submit RFCs. If you want to help decide what Rust code should look like, come get involved! We're making good progress and the style is coming together. If you want to see the style in practice, check out our example or use the Integer32 Playground and select 'Proposed RFC' from the 'Format' menu. Be aware that implementation is work in progress. Issues in final comment period: [macro_use] on the same line as crate trait bounds Specify rules for breaking long where conditions Single-line where Combining openings and closings Good first issues: We're happy to mentor these, please reach out to us in #rust-style if you'd like to get involved paths simple expressions assignment and assignment operators control flow Upcoming Events Jun 21. Rust Meetup Dresden. Jun 21. Rust Community Team Meeting at #rust-community on irc.mozilla.org. Jun 21. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org. Jun 24. RainOfRust Camp Ahmedabad, Gujarat. Jun 24. Rust Workshop Bangalore - Rain of Rust. Jun 27. Rust Zurich - June Meetup. Jun 27. Cambridge Rust Meetup. Jun 27. Let's Rust - Hyderabad. Jun 27. RainOfRust Camp Patan, Gujarat. Jun 28. Boston Rust - Tutorial Bug-fixing Hackathon. Jun 28. OpenTechSchool Berlin - Rust Hack and Learn. Jun 28. Rust Community Team Meeting at #rust-community on irc.mozilla.org. Jun 28. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org. Jun 29. Rust release triage. Jun 29. Rust Durham, NC - Welcome to Rust! Introductions and Lightning Talks. Jun 3. Rust Prague Meetup. Jul 4. Rust Utrecht - Rust Workshop. Jul 5. Rust Atlanta - Grab a beer with fellow Rustaceans. Jul 5. Rust Community Team Meeting at #rust-community on irc.mozilla.org. Jul 5. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org. If you are running a Rust event please add it to the calendar to get it mentioned here. Email the Rust Community Team for access. Rust Jobs Senior Research Engineer - Servo at Mozilla. Tor: Summer 2017 Internship to Create a Bridge Bandwidth Scanner. Student Research Assistant for developing Clippy in Karlsruhe (contact oliver.schneider \at kit.edu). Tweet us at @ThisWeekInRust to get your job offers listed here! Quote of the Week impl Clone for T { fn clone(&self) -> T { unsafe { std::ptr::read(self) } } } — @horse_rust on twitter. Thanks to llogiq for the suggestion. Submit your quotes for next week! This Week in Rust is edited by: nasa42, llogiq, and brson. [Less]
Posted 5 days ago by Corey Richardson
Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust ... [More] or send us a pull request. Want to get involved? We love contributions. This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR. Updates from Rust Community News & Blog Posts RustConf 2017 tickets are now available. encoding_rs, a new character encoding conversion library written in Rust, has landed in nightly Firefox. Bugs you'll probably only have in Rust. Why not to use Rust. Algorithms cookbook in Rust. Implementing cooperative multitasking in Rust. Switching from C++ to Rust. Graphics by squares: a gfx-rs tutorial. Rustfmt releases. There are some significant changes happening to Rustfmt. Here is what you need to know. System programming in Rust: beyond safety. Writing a LALR(1) parser generator in Rust. hyper v0.11 is released. This week in Redox 22. This week in Servo 104. Crate of the Week This week's crate is include_dir, a crate that lets you include entire directory contents in your binary – like include_str!, but on steroids. Thanks to Michael Bryan for the suggestion! Submit your suggestions and votes for next week! Call for Participation Always wanted to contribute to open-source projects but didn't know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started! Some of these tasks may also have mentors available, visit the task page for more information. [easy] rust: Guard types should implement more traits. walkdir: Add Error docs to methods that return Result. walkdir: Default to generating constified enums, rather than generating Rust enums. walkdir: Change OsString args in sort_by to OsStr. walkdir: Remove re-export of is_same_file. walkdir: Document why unwraps won't fail. walkdir: Make skip_current_dir and filter_entry inherent methods. walkdir: Link references to std in docs. walkdir: Add build badges to Cargo.toml. walkdir: Implement Debug for WalkDir, Iter and IterFilterEntry. walkdir: Correct errors in WalkDir type docs. walkdir: Document that Iter and IterFilterEntry are the result of trait methods. walkdir: Add links to other walkdir items in WalkDirIterator docs. walkdir: Add links to other walkdir items in Iter and IterFilterEntry docs. walkdir: Add links to other walkdir items in DirEntry docs. walkdir: Add example for content_first. rust-cookbook: Use filter_entry in walkdir examples. [easy] rust-bindgen: Default to generating constified enums, rather than generating Rust enums. [less-easy] rust-bindgen: Rewrite is_unsized as either a graph traversal or fix-point analysis. [less-easy] rust-bindgen: Rewrite can_derive_debug as either a graph traversal or fix-point analysis. [less-easy] rust-bindgen: Rewrite can_derive_copy[_in_array] as either a graph traversal or fix-point analysis. [less-easy] rust-bindgen: Rewrite has_vtable checks as either graph traversal or fix-point analysis. If you are a Rust project owner and are looking for contributors, please submit tasks here. Updates from Rust Core 122 pull requests were merged in the last week. overflow-check str index by inclusive (...) ranges float min/max is now pure Rust Ord::{min, max} allocation-less Display for Path and OsStr suggest == on inadvertent assignment in if conditions omit trait errors implied by other errors save-analysis is now JSON only collections is back fix type inference ICE due to missing obligations fix fn pointer coercion ICE use custom cargo/rustc paths when parsing flags cargo stores API tokens in separate, user-private file New Contributors Marco Castelluccio Thomas Lively Wonwoo Choi Approved RFCs Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week: RFC 1974: Prepare global allocators for stabilization. Final Comment Period Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now. This week's FCPs are: [disposition: postpone] Allow extern crate to take a list of crates. [disposition: merge] Stabilize drop order. [disposition: merge] Specify #[repr(transparent)]. [disposition: merge] Conversions from &mut T to &Cell. [disposition: merge] Tiered browser support policy for Rust's web content. New RFCs Experimentally add coroutines to Rust. Add a try_with method to LocalKey, replacing the existing but unstable state method Style RFCs Style RFCs are part of the process for deciding on style guidelines for the Rust community and defaults for Rustfmt. The process is similar to the RFC process, but we try to reach rough consensus on issues (including a final comment period) before progressing to PRs. Just like the RFC process, all users are welcome to comment and submit RFCs. If you want to help decide what Rust code should look like, come get involved! We're making good progress and the style is coming together. If you want to see the style in practice, check out our example or use the Integer32 Playground and select 'Proposed RFC' from the 'Format' menu. Be aware that implementation is work in progress. Issues in final comment period: [macro_use] on the same line as crate trait bounds Specify rules for breaking long where conditions Single-line where Combining openings and closings Good first issues: We're happy to mentor these, please reach out to us in #rust-style if you'd like to get involved paths simple expressions assignment and assignment operators control flow Upcoming Events Jun 21. Rust Meetup Dresden. Jun 21. Rust Community Team Meeting at #rust-community on irc.mozilla.org. Jun 21. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org. Jun 24. RainOfRust Camp Ahmedabad, Gujarat. Jun 24. Rust Workshop Bangalore - Rain of Rust. Jun 27. Rust Zurich - June Meetup. Jun 27. Cambridge Rust Meetup. Jun 27. Let's Rust - Hyderabad. Jun 27. RainOfRust Camp Patan, Gujarat. Jun 28. Boston Rust - Tutorial Bug-fixing Hackathon. Jun 28. OpenTechSchool Berlin - Rust Hack and Learn. Jun 28. Rust Community Team Meeting at #rust-community on irc.mozilla.org. Jun 28. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org. Jun 29. Rust release triage. Jun 29. Rust Durham, NC - Welcome to Rust! Introductions and Lightning Talks. Jun 3. Rust Prague Meetup. Jul 4. Rust Utrecht - Rust Workshop. Jul 5. Rust Atlanta - Grab a beer with fellow Rustaceans. Jul 5. Rust Community Team Meeting at #rust-community on irc.mozilla.org. Jul 5. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org. If you are running a Rust event please add it to the calendar to get it mentioned here. Email the Rust Community Team for access. Rust Jobs Senior Research Engineer - Servo at Mozilla. Tor: Summer 2017 Internship to Create a Bridge Bandwidth Scanner. Student Research Assistant for developing Clippy in Karlsruhe (contact oliver.schneider \at kit.edu). Tweet us at @ThisWeekInRust to get your job offers listed here! Quote of the Week impl Clone for T { fn clone(&self) -> T { unsafe { std::ptr::read(self) } } } — @horse_rust on twitter. Thanks to llogiq for the suggestion. Submit your quotes for next week! This Week in Rust is edited by: nasa42, llogiq, and brson. [Less]
Posted 6 days ago
Here’s what happened on the MozMEAO SRE team from June 13th - June 20th. Current work Static site hosting The irlpodcast site now has a staging environment also hosted in S3 with CloudFront. Additionally, Jenkins has been updated to ... [More] deploy to staging and production via git push. We’re going to move viewsourceconf.org from Kubernetes to S3 and CloudFront hosting. Production and staging environments have been provisioned, but we’ll need to update Jenkins to push changes to these new environments. Basket move to Kubernetes Basket will switch to HTTPS only. Kubernetes (general) Our DataDog, New Relic and MIG DaemonSets have been configured to use Kubernetes tolerations to schedule pods on master nodes. This allows us to capture metrics from K8s master nodes in additional to worker nodes. Frankfurt Kubernetes cluster provisioning Work continues to enable our apps in the new Frankfurt Kubernetes cluster. In addition, we’re working on automating our app installs as must as possible. MDN ElasticSearch will be upgraded to 2.4 in SCL3 production, June 21 11 AM PST We may reconsider self-hosting ElasticSearch. Links Github project tracking SRE work How MozMEAO SRE’s work Weekly SRE meeting notes [Less]
Posted 6 days ago by Daniel Stenberg
(Note: this blog post as been updated as the command line option changed after first publication, based on comments to this very post!) curl is arguably a “Swiss army knife” of HTTP fiddling. It is one of the available tools in the toolbox with a ... [More] large set of available switches and options to allow us to tweak and modify our HTTP requests to really test, debug and torture our HTTP servers and services. That’s the way we like it. In curl 7.55.0 it will take yet another step into this territory when we finally introduce a way for users to send “OPTION *” and similar requests to servers. It has been requested occasionally by users over the years but now the waiting is over. (brought by this commit) “OPTIONS *” is special and peculiar just because it is one of the few specified requests you can do to a HTTP server where the path part doesn’t start with a slash. Thus you cannot really end up with this based on a URL and as you know curl is pretty much all about URLs. The OPTIONS method was introduced in HTTP 1.1 already back in RFC 2068, published in January 1997 (even before curl was born) and with curl you’ve always been able to send an OPTIONS request with the -X option, you just were never able to send that single asterisk instead of a path. In curl 7.55.0 and later versions, you can remove the initial slash from the path part that ends up in the request by using –request-target. So to send an OPTION * to example.com for http and https URLs, you could do it like: $ curl --request-target "*" -X OPTIONS http://example.com $ curl --request-target "*" -X OPTIONS https://example.com/ In classical curl-style this also opens up the opportunity for you to issue completely illegal or otherwise nonsensical paths to your server to see what it does on them, to send totally weird options to OPTIONS and similar games: $ curl --request-target "*never*" -X OPTIONS http://example.com $ curl --request-target "allpasswords" http://example.com Enjoy! [Less]